Another JS Registry. Seriously?!

oh shouldn't it be tsr ?

Amazing im so happy to see this!

Deno was launched with a strong argument against centralized package repositories. Why is this not federated from the start?

Thank you.

I feel esm only will throw 90% of node projects as of today. I don’t see myself using it as several libraries I depend on doesn’t have ESM.
I get the feeling that in near future the benefits will be monetised to pay the server cost to run the transpilation etc on server side.

Javascript is a plague

ahahahahahahahahaahahahahahahahahahahahahaahahahah this is sooooooooo funnyyy)))))) really. Trying to solve problems that not even exist lol

Can I <script src=“url”> it or do I have to npx it?

Despite the natural scepticism around, I'm really happy that somebody actually decided to build JSR.
Thanks and good luck!

Is there a way to publish the sources?

For example, for Vue libraries it makes a lot of sense to publish the source alongside the esm/cjs/umd, because using source directly leads to better tree-shaking.

It's far better than NPM, but…

Why not do it like Go ?

First you need to make sure deno demo work first 😂
Its unhinged that a simple install demo does not work as is especially in older server environment

The main highlight for me is the open ID things to publish packages, something npm does wrong. If you are optimizing for maintainers, downloads stats are critical IMHO.

Is the audio AI generated? It makes me feel strange.

This is really cool.

Damn ... This will definitely be the norm ❤️🙌

It happened!!

so npm users can't use my package now? if so how is it possible?

this is why I love competition <3

i just use git://

Deno hired Awesome !

how secure is this?

Brilliant

Is the narrator is 'awesome' ?

I'd argue NPM is a complete heckshow (self censored expletive). How many times have we installed something into an existing project and we get that "Cannot resolve dependency tree" error. Some dependency deep down your tree is not peer-compatible with something else you have installed, and good luck finding what it is, since these error messages are so verbose and really offer no suggestion on how to fix it. If NPM is to survive, its DX needs drastic improvement.

Oh. Don't get me started on these single-function packages like is-odd. It'd be nice to have a JSR somewhere that's curated and administered so low-quality libraries don't get published.

Having auto generated docs is huge!

no-god-please-no-michael-scott.gif

dep.ts is best in deno about node that need this solution.

npm is too annoying this is good

honestly .. it is already bad because it interops with NPM ... npm is not bad for the reasons you mentioned but because of the dependency-hell it generates

Its a bit rocky for packages not using deps already on JSR, but this is reallt cool. It'll get better with time

man npm reallly is the battle tested....npm install everything.

how does iot handle exports , like i want a componet library that puts @ui/button and @ui/accordion separately because one need a use client to play nice with rscs but the other can be used directly in an RSC

I am curious about why you chose to have a "jsr.json" file instead of "jsr.ts" file? Adding support for a typescript config file would provide so many benefits.

It could have been broken into two separate videos

Can reactjs able to use jsr?

This is a major improvement of the JS ecosystem, lovely <3

looks good

It good for package publisher not for end user I think pnpm is better

I'm sure JSR will take over NPM's job as it doesn't do it well enough. I'll be waiting for that day.

What about browser compatibility?

this looks very cool