Ryan Dahl

And so you can actually import JSR NPM packages like in the NPM format directly in Node, for example, just by setting some stuff in your NPM RC file. So there is a little bit of like a one line sort of setup to be able to pull in JSR packages that in, in a node project directly from, from JSR. But, uh, yeah, nevertheless, people, people are also often posting things to, to NPM.

And so you can actually import JSR NPM packages like in the NPM format directly in Node, for example, just by setting some stuff in your NPM RC file. So there is a little bit of like a one line sort of setup to be able to pull in JSR packages that in, in a node project directly from, from JSR. But, uh, yeah, nevertheless, people, people are also often posting things to, to NPM.

And it's, it's a feature that we're kind of dwelling on right now about whether we should support it. It'd be pretty easy to, to like allow people to post to JSR and then auto post to NPM just to, just to kind of have, uh,

And it's, it's a feature that we're kind of dwelling on right now about whether we should support it. It'd be pretty easy to, to like allow people to post to JSR and then auto post to NPM just to, just to kind of have, uh,

uh in npm first uh experience um you know if that helps people i think that's that might be worthwhile doing but yeah generally you know the the the broad strokes of of everything i'm undertaking here is like let's level up javascript let's just make this nicer let's strive to make this nicer and uh yeah if you use if you use jsr either as a consumer or a publisher

uh in npm first uh experience um you know if that helps people i think that's that might be worthwhile doing but yeah generally you know the the the broad strokes of of everything i'm undertaking here is like let's level up javascript let's just make this nicer let's strive to make this nicer and uh yeah if you use if you use jsr either as a consumer or a publisher

you will be delighted, like, you know, auto-generated documentation. Like, why does JavaScript not have auto-generated documentation? Like, you know, with everybody writing stuff in TypeScript these days, like, we have all the information available, and yet, you know, somehow NPM does not have this feature. Like, we need to make some progress here, and clearly Microsoft is not doing that.

you will be delighted, like, you know, auto-generated documentation. Like, why does JavaScript not have auto-generated documentation? Like, you know, with everybody writing stuff in TypeScript these days, like, we have all the information available, and yet, you know, somehow NPM does not have this feature. Like, we need to make some progress here, and clearly Microsoft is not doing that.

Microsoft slash GitHub, I should say.

Microsoft slash GitHub, I should say.

I mean, auto-generated docs, for example, is, is something that's, that's going to help you. We have something called the JSR score, which is stolen from, from Dart actually, where we kind of rank packages. We give you a better score if you follow best practices. So

I mean, auto-generated docs, for example, is, is something that's, that's going to help you. We have something called the JSR score, which is stolen from, from Dart actually, where we kind of rank packages. We give you a better score if you follow best practices. So

you know, we don't force you to, to do all this rigmarole upfront because, you know, sometimes you just want to publish something and don't, don't want to do too much, but, uh, you, you kind of get this signal about like how, what, what sort of best practices are, are people following? Like, are they, are they adding doc strings to all of their exported modules?

you know, we don't force you to, to do all this rigmarole upfront because, you know, sometimes you just want to publish something and don't, don't want to do too much, but, uh, you, you kind of get this signal about like how, what, what sort of best practices are, are people following? Like, are they, are they adding doc strings to all of their exported modules?

Are, are they, do they have a readme? Do they have a license file? This, this sort of thing, you know, it's, it's generally much more searchable. You can search through symbols. You can, uh, It allows you to pull in TypeScript types nicely. If those packages are written in TypeScript, there's not like a definitively typed thing that you also need to know about.

Are, are they, do they have a readme? Do they have a license file? This, this sort of thing, you know, it's, it's generally much more searchable. You can search through symbols. You can, uh, It allows you to pull in TypeScript types nicely. If those packages are written in TypeScript, there's not like a definitively typed thing that you also need to know about.

Yeah, it's generally a good experience. But yeah, I would say the real 10x behavior is when you publish, then it's like, oh my God, I can't believe it's so simple. Or rather, now I recognize how terrible NPM publishing actually is.

Yeah, it's generally a good experience. But yeah, I would say the real 10x behavior is when you publish, then it's like, oh my God, I can't believe it's so simple. Or rather, now I recognize how terrible NPM publishing actually is.

That's right. Yeah, you can mark in your package which runtimes are supported and that displays it on the package page. And so there are modules posted to JSR that have nothing to do with Deno, right? Browser only or for Bun, for example. It is not Deno specific. That's awesome.

That's right. Yeah, you can mark in your package which runtimes are supported and that displays it on the package page. And so there are modules posted to JSR that have nothing to do with Deno, right? Browser only or for Bun, for example. It is not Deno specific. That's awesome.