Nicholas Zakas

You actually had to apply for it and prove that like you're the right person to be handling that scope.

And they approved me really quickly because they knew who I was and that I was involved with ESLint.

So I was able to get that.

They had trusted publishing right from the start, or else you have to use two-factor authentication to publish locally.

No pre-install or post-install scripts.

There's just a lot that was really good about JSR.

And it basically suffered the same fate as NPM, just on a much faster timeline.

which was basically, there was a lot of interest early on, a lot of activity, a lot of iteration.

I was filing issues on the JSR GitHub repo.

They were getting answered sometime within hours and things just getting fixed and pushed out.

But

Eventually, that timeline started expanding to the point where I wasn't getting any responses anymore.

Even to bug reports, there was... I mean, I was finally able to get one response when a new version of Deno was pushed out and that broke...

the command line, the JSR command line tool, was finally able to get a response from them to get that fixed fairly quickly.

They had announced that it was going to be an open governance registry for JavaScript, and they had formed a committee that had people from like NPM and Deno and I think OpenJS Foundation and Vault, and that just kind of went nowhere.

There hasn't been any updates since then.

Like JSR is still running, but as far as I can tell, it's mostly an abandoned project at this point.

And there's just some of the Deno diehards like really like to use it, but it doesn't seem like it's ever going to be a real competition for NPM registry.

So pre-install and post-install scripts on NPM are designed to let you run additional commands after install.

in order for a package to work.