Publish vite to jsr.io

[o-az]

Are you open to publishing vite to jsr.io alongside npm registry?

some examples of projects that have started publishing to jsr:

Hono
https://deno.com/blog/hono-on-jsr

Supabase
https://deno.com/blog/supabase-on-jsr

On your end you just need to signup and claim the @vite scope. Then I'm happy to make a PR and take care of the rest

[bluwy]

I’ve asked this with the team, and we found that it’s a lot of maintenance to publish raw TS files, manage bundled dependencies, handle inlined types etc that it’s not worth publishing to JSR at the moment.

You mentioned willing to make a PR for the initial setup, but I think the maintenance thereafter is something we want to avoid for now. Maybe we can revisit this in the future if JSR has a laxer publishing rules. (Or if they do but we missed it)

[o-az]

I’ve asked this with the team, and we found that it’s a lot of maintenance to publish raw TS files, manage bundled dependencies, handle inlined types etc that it’s not worth publishing to JSR at the moment.

You mentioned willing to make a PR for the initial setup, but I think the maintenance thereafter is something we want to avoid for now. Maybe we can revisit this in the future if JSR has a laxer publishing rules. (Or if they do but we missed it)

Thank you for your reply. Your reasoning makes sense.

[maliknajjar]

Isn't JSR a superset of npm? Based on my understanding of how JSR works, if you publish your package to JSR, it will automatically be available on npm as well. So, you only need to maintain it in one place (JSR)

[rschristian]

Isn't JSR a superset of npm?

This is marketing and dubious at best; I think it's best ignored.

if you publish your package to JSR, it will automatically be available on npm as well.

This isn't the case, no. How would they do this? They don't have publishing rights for all the equivalent names & namespaces on NPM.

If you're referring to the @jsr scope, it's a fake scope that they use as an alias to point at a different registry; packages aren't mirrored to NPM.

[maliknajjar]

What I mean is that you can publish Vite on JSR, and JSR will take care of transpiling it to ensure compatibility with Node.js and other JavaScript runtimes. It doesn't really matter how you install it—whether through the JSR scope in npm or using npx. The key point is that you can publish it in one place, JSR, and make it accessible across various JavaScript runtimes. This way, you only need to maintain it in one location.

One of the great things about JSR is that you can publish the TypeScript code directly, and JSR will automatically handle the transpilation to JavaScript and generate the .d.ts files for your project. This means you won’t have to manage that process yourself or set up CI/CD steps to transpile your TypeScript files into JavaScript for compatibility.

Since Vite can be used with Deno and Bun, it makes sense to migrate it to a package manager like JSR, which is designed for multiple JavaScript runtimes.

[rschristian]

The key point is that you can publish it in one place, JSR, and make it accessible across various JavaScript runtimes.

The key issue there is that users need additional setup in order to consume from JSR, which makes it a non-starter. Can't expect people to configure installing from another repository to use something as popular as Vite, and publishing to NPM and JSR adds little value.