-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Investigate impact of Deno moving its std library to JSR #571
Comments
For those of us using Deno, it would be good if all of the packages could be published on JSR. |
I am with you on this, JSR stands to greatly simplify my work of deploying this project to support as many runtimes as I target. The one thing that seems a little suboptimal for me right now is the need to use Is anyone on the NPM side of JS runtimes working to add first-class support for JSR package installations? |
I'm going to add this conversation to this issue: tl;dr: Technically @simplewebauthn/browser is available via https://deno.land/x/simplewebauthn@v11.0.0/packages/browser, but its code is not in a shape that Deno recognizes (no file extensions on relative imports, etc...) Could migrating/deploying this project to JSR make @simplewebauthn/browser available in Deno projects too? |
If anyone's following this issue and is interested in testing out Deno support via JSR-hosted versions of v11.0.0, check out this discussion comment for more info: |
Describe the issue
See https://deno.com/blog/std-on-jsr, this part makes me wonder if I have to start using JSR in here, which would have an impact on the rest of the project:
The text was updated successfully, but these errors were encountered: