Skip to content

Proposal: Support JSR for Remix 3 distribution #10991

@nestarz

Description

@nestarz

Hey folks,

The "Religiously Runtime" philosophy in Remix 3 seems like a perfect match for JSR. Since you’re prioritizing Web APIs and ESM without bundler interference, JSR would let you publish your TypeScript source directly.

This fits the "Model-First" goal perfectly—LLMs and developers get clean source and auto-generated docs without a transpilation build step. It also ensures the packages work natively across Node, Deno, and Bun. Since JSR is a superset of npm, it doesn't break existing workflows; it just makes the "portable by default" promise easier to maintain.

The main benefit is a zero-config build pipeline for your sub-packages. The only real cost would be adding a jsr.json file to the repo.

More info:
https://jsr.io/docs/why
https://jsr.io/docs/with/node
https://jsr.io/docs/with/vite
https://jsr.io/docs/governance/overview (it's backed by major contributors to OSS in Javascript ecosystem)

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions