Investigate JSR

[stefnotch]

I would love to look into the JSR, since it is being backed by the creator of Node.js and has an open governance board.

From a practical perspective, it would also be useful for us to be able to use their auto-generation of an API documentation.

We will still want to dual-publish to npm, to cover every use-case. Especially library authors will want to use the jsr version if they publish to the jsr, and the npm version if they publish to npm.
It seems like there is a proposal to make it possible to have dependencies that depend on a different registry, but even npm does not support them

[stefnotch]

jsr-io/jsr#701 (comment)

The tarball URL seems to already be in the lockfile. So for the dual publishing to npm, maybe there's a way of publishing a dummy package to npm

1. dummy package depends on JSR
2. dummy package's lockfile points at JSR
3. create a shrinkwrap file for the dummy package https://docs.npmjs.com/cli/v11/configuring-npm/npm-shrinkwrap-json
4. re-export everything through the dummy package
5. publish that to npm

Biggest downside is that step 3 means that the dummy package is stops transitive dependency upgrades. I think that's fine, since we can treat wesl as being dependency free.

[stefnotch]

Or maybe simply setting the "publishConfig":{"registry":"http://my-internal-registry.local"} field in such a dummy package would do the trick? Since we could treat wesl as only having JSR dependencies, aka being scoped to that registry.

[mighdoll]

+1 for dual publishing, the mainstream is on npm, but appealing to the pioneers on JSR too is goodness.