Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: Integrity check failed for remote specifier. The source code is invalid, as it does not match the expected hash in the lock file. #194

Closed
kachick opened this issue Jan 16, 2025 · 2 comments · Fixed by #195
Labels
bug Something isn't working

Comments

@kachick
Copy link
Owner

kachick commented Jan 16, 2025

https://github.com/kachick/depop/actions/runs/12800649376/job/35688791738

nix develop --command deno task all

error: Integrity check failed for remote specifier. The source code is invalid, as it does not match the expected hash in the lock file.

  Specifier: https://esm.sh/v135/[email protected]
  Actual: f513c98f7bc98331b687de4ec8387e6b4174c56596213b7d73b85641bdc28697
  Expected: 52480d4c00855e4f76843caa4f2818eb001671523740cbf064cbd108721c29c8

This could be caused by:
  * the lock file may be corrupt
  * the source itself may be corrupt

Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server.

looks like similar of #143

@kachick kachick added the bug Something isn't working label Jan 16, 2025
@kachick kachick added this to 🛸 Jan 16, 2025
@github-project-automation github-project-automation bot moved this to 🙋‍♂ in 🛸 Jan 16, 2025
@kachick
Copy link
Owner Author

kachick commented Jan 16, 2025

https://github.com/esm-dev/esm.sh/releases/tag/v136 has been released in 3 days ago

@kachick
Copy link
Owner Author

kachick commented Jan 16, 2025

The build version prefix of esm.sh was introduced to avoid potential breaking changes caused by updates to the esm.sh server. However, it can lead to duplication issues when updating the server. In v136, we have removed the build version prefix from the module path, and the ?pin query will be ignored. Paths with the build version prefix will continue to work as before, but the new default will be paths without the build version prefix.

#143 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🎉
Development

Successfully merging a pull request may close this issue.

1 participant