We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
allowRemoteModules=false doesn't work when using npm: specifier
await EdgeRuntime.userWorkers.create({ servicePath, memoryLimitMb, workerTimeoutMs, noModuleCache, allowRemoteModules: false, ... });
import * as jose from 'npm:jose'
It should result in worker boot error failed to load 'npm:something', A remote specifier was requested, but --no-remote is specified.
BUT, it import remote module successfully, while https:// or jsr: prefix works and result in "--no-remote is specified" error
npm specifier still loaded from remote
while jsr specifier can result in expected error:
The text was updated successfully, but these errors were encountered:
EmitterFactory
allow_remote_modules
no npm
🎉 This issue has been resolved in version 1.50.1 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Sorry, something went wrong.
wow, so fast
nyannyacha
Successfully merging a pull request may close this issue.
Bug report
Describe the bug
allowRemoteModules=false doesn't work when using npm: specifier
To Reproduce
Expected behavior
It should result in
worker boot error failed to load 'npm:something', A remote specifier was requested, but --no-remote is specified.
BUT, it import remote module successfully, while https:// or jsr: prefix works and result in "--no-remote is specified" error
Screenshots
npm specifier still loaded from remote
while jsr specifier can result in expected error:
The text was updated successfully, but these errors were encountered: