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

Integrity check with data uri dynamic imports support #16120

Open
zifeo opened this issue Oct 1, 2022 · 0 comments
Open

Integrity check with data uri dynamic imports support #16120

zifeo opened this issue Oct 1, 2022 · 0 comments

Comments

@zifeo
Copy link

zifeo commented Oct 1, 2022

According to Deno's documentation:

Like caching above, you can also use the --lock=lock.json option during use of the deno run sub command, validating the integrity of any locked modules during the run. Remember that this only validates against dependencies previously added to the lock.json file. New dependencies will be cached but not validated.

However this seems to be outdated/not true as it fails when using dynamic imports:

error: The source code is invalid, as it does not match the expected hash in the lock file.
  Specifier: data:text/javascript,REDACTED
  Lock file: lock.json

I would expect to have no validation on specifier not included in the lock file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant