Investigate impact of Deno moving its std library to JSR

[MasterKale]

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:

deno.land/std will still be available indefinitely. All programs that depend on deno.land/std will keep working. Don’t worry!

However, going forward new features will be published to jsr.io/@std. deno.land/std will receive only critical updates, such as security patches.

[sachaw]

For those of us using Deno, it would be good if all of the packages could be published on JSR.
Would be nice in the future to see this project use JSR as the package source for NPM (using JSR's automatic transpiling)
This could possibly remove the need to use DNT.

[MasterKale]

Would be nice in the future to see this project use JSR as the package source for NPM (using JSR's automatic transpiling)
This could possibly remove the need to use DNT.

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 npx jsr add to install something, and remember to commit the generated .npmrc to help future npm install commands know where to pull in SimpleWebAuthn.

Is anyone on the NPM side of JS runtimes working to add first-class support for JSR package installations?