You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
According to Deno's documentation:
However this seems to be outdated/not true as it fails when using dynamic imports:
I would expect to have no validation on specifier not included in the lock file.
The text was updated successfully, but these errors were encountered: