You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think JSR certainly addressed a lot of upfront friction of publishing package. For most people, having modern tooling / infra for code share / reuse is huge boost of their productive that focus on coding itself.
Nowadays I rarely have to reach Node.js and npm for the needs that are now completely taken over by Deno, from small CLI or even full featured Hono web app that deployable on both Deno Deploy or Cloudflare Workers.
IMO, the top one laggy of JSR / Deno Deploy is that they were only tied to GitHub account / infra, if JSR to add support only barely minimum support of Git repo like SourceHut or even GitWeb, that would relieve people from all the bloated features of GitHub and further escape from Microsoft who busy betting on AI instead of addressing decades long UX, DX and security needs of the ecosystem.
I managed to migrate to all-in JSR by changing only one-liner of import mapping:
Thanks!
The text was updated successfully, but these errors were encountered: