-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support npm: specifiers #314
Comments
Any update on this issue? |
The Deno blog mentions that |
I must say, from a fresh user (excuse the pun), this information wasn't obvious to me. Had I been forewarned, I would have avoided the route I ended up taking. Is it possible to make this caveat a bit more visible? What are the isolated issues that need to be closed in order to have this feature? Looking for other ways to import package so that I can remain on deno deploy. Just when I thought I was done developing :(. Is there not a way for a warning to appear during |
Well, I think there is a workaround: if the deno bundle supports the |
I dont think the bundle/pack command supports npm specifiers yet 😢 |
Status update: we are working towards supporting |
Is there a way to work around this with import maps? I have this error
I tried this import map but no luck: {
"imports": {
"npm:protocol-buffers-schema": "https://esm.sh/[email protected]"
}
} |
@nzoschke I think you would have to do {
"imports": {
"npm:[email protected]": "https://esm.sh/protocol-buffers-schema"
}
} |
any update on this? |
I think they just announced |
Perhaps this is what you're referring to @vixalien? Looks like you might be right that support in |
Update: Deno Deploy supports node builtins now! |
seems it's just
|
Yes you are right, but node specifiers are already supported, will npm be far away? :) |
Npm specifiers don't work on deno deploy denoland/deploy_feedback#314
Are there any new updates on this? |
It's finally here. 💥 |
npm:
specifiers are stable now, but Deno Deploy still doesn't support it.The text was updated successfully, but these errors were encountered: