Publish to JSR alongside NPM

[flevi29]

Why JSR

• https://jsr.io/docs/why
• primarily because it is the default registry for deno, but also it's striving to be (and already is a superset of) the replacement for npm with the goal of supporting every runtime equally
• secondarily, because it auto-generates documentation, easily switchable between versions, this way we wouldn't need typedoc and additional build step for it and configuration https://jsr.io/docs/writing-docs
  • we should also replace the lengthy README.md documentation with a link to the superior JSR page, but really we should already be doing this with the typedoc docs on github pages
• it also builds everything from TypeScript source files, so we wouldn't need any build step, at least not for JSR, in theory, still need to experiment with this

[curquiza]

Hello @flevi29
Thanks for opening the issue.
I would rather we wait for more feedback from the community, before doing it. It's important we implement it when it's a real need from users to avoid adding too much maintenance on our side (we are a small team)

So thank you for having opened the issue, it starts the discussion with the community. If you are a user and reading this issue, if you need this, feel free to interact here and raise your voice here ✋

[flevi29]

I'd argue the overall maintenance requirements would stay the same, it's mostly a replacement for typedoc for us, even though it's so much more. The end user will be unaffected for the most part, with the added ability to pull this package from JSR as well. Our build step wouldn't need to bother with documentation anymore. Of course I'm just floating the idea.

Supabase and Hono are already on JSR and they're pretty big players:
https://deno.com/blog/supabase-on-jsr
https://deno.com/blog/hono-on-jsr

We could be another "early" -ish supporter, with little to no technical debt and no real cons, as far as I see it, probably even future proof.