Skip to main content
Aleksandr Shoronov
Telegram logo Mastodon logo

Another package registry

When I was on FOSDEM this year in the talk of Leo Kettmeir from Deno, he talked about closed beta access to their new package registry — JSR . I kept not so much attention to it. Recently, with announcement of public beta access, discussions around the Internet started to appear.

First of all, JSR is drived by deno community. So I think it's obvious motivation to create package manager and registry for Deno. Yes, JSR is positioned as a package registry not only for Deno, but for usage with Node.js, browsers, etc through npm and yarn. But I think it's not the main goal anyway. At least reply of JSR developer Luca Casonato doesn't give me any confidence in it:

Well, yes, for ten recent years of npm, their pages of packages got just only TS icon and files tab. But what else we actually need from package registry web interface? Usually I take a look on README, versions, dependencies, statistics of downloads and link to source code.

JSR supports automatic building of your .d.ts files, but usually my CD pipeline doing it and I can control it. Moreover, not every package actually needs it, and I won't be happy when package registry will spend time and resources to do things nobody needs.

JSR will automatically generate docs from your typings. This feature seems good to me. At least from what I see from Rust ecosystem, for example: developers there use by default good de facto default documentation system, and it's good to have it in JS/TS world too.

JSR modules can be used in Node, Deno, Bun, Cloudflare Workers, and more.

Okay, but I can use npm and yarn (maybe shouldn't the last one) packages in all these environments too.

I don't want to be too conservative and I'm open to new things. But I super tired of marketing bullshit and hypnotic unclear messages from every new framework, tool, registry which want really change the world and replace everything around you.