Nicholas Zakas

I think they got a lot of stuff right.

But one of the challenges, again, like having a competitor to NPM is like, number one, you can't actually do quote unquote binaries like ESLint on JSR.

You can't just say like JSR install ESLint and then just run ESLint.

It doesn't work that way.

And then two, any alternative to NPM needs to be compatible with NPM.

Because unless you're able to use all of the packages just on that new registry, you're going to have to mix and match between NPM and that new registry.

And that's also something that JSR just did not get right.

If you try to use JSR packages in with NPM packages in a package that you want to publish, just straight up doesn't work.

Because we tried to do this with one of our ESLint packages because...

The nice thing about JSR is Deno published a bunch of standard library-type packages on there, and they're really good.

And so we wanted to use one in one of our packages, and it ended up being such a pain that we just copied the source code from the JSR package into our repo so we could package it and publish it up onto NPM.

So that story was just not there at all.

It was okay if you were just building an application that you were not going to be publishing to NPM.

You're just going to be deploying.

That worked okay.

But then going and publishing that back to NPM just did not work at all.

Yeah.

Yeah, I don't think so.

And part of the reason is,

it seems like a lot of developers are very skeptical of AI companies and providing data that can be used to train AIs.