Skip to content

[Feature] Publish to JSR for first-class Deno consumption #442

Description

@pathosDev

Rationale

Deno is a first-class runtime (smoke-tested in CI), but Deno users consume the package via the npm compatibility layer. JSR is Deno's native registry with first-class TypeScript resolution; publishing there removes friction for a whole runtime community at near-zero maintenance cost.

Scope

  • jsr.json (name, version, exports mirroring the package.json exports map).
  • Publish step in .github/workflows/publish.yml via OIDC (same trusted-publishing model as npm; version-guarded so re-runs stay safe).
  • npm remains the canonical registry; JSR is an additional channel.

Documentation

README + install docs: JSR install command for Deno (EN + DE); CHANGELOG.

Acceptance

  • deno add jsr:... works in a scratch project; smoke case runs against the JSR artifact; publish workflow green and idempotent.

Non-goals

Deno-specific API surface; dropping the npm compatibility path.

Relates

Subpath exports #414 (exports map is the JSR export source). Improvement program M3/M8.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestinfrastructureCI / build / live-integration testspriority: lowNice-to-have / niche / demand-driven

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions