Skip to content
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

Good to be npm-free #29

Open
imcotton opened this issue Jan 14, 2025 · 2 comments
Open

Good to be npm-free #29

imcotton opened this issue Jan 14, 2025 · 2 comments

Comments

@imcotton
Copy link

I managed to migrate to all-in JSR by changing only one-liner of import mapping:

   "imports": {
-    "micro-key-producer/ssh.js": "npm:micro-key-producer@~0.7.0/ssh.js"
+    "micro-key-producer/ssh.js": "jsr:@paulmillr/micro-key-producer@~0.7.3/ssh.js"
   },

Thanks!

@paulmillr
Copy link
Owner

Perfect. What’s your impression of jsr / deno so far?

@imcotton
Copy link
Author

imcotton commented Jan 14, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants