A modern package registry for JavaScript and TypeScript
summary
JSR claims to be a drop‑in replacement for npm that accepts original TypeScript, runs a trusted transpiler inside the registry to emit per‑runtime artifacts (Node JS, Deno, browser), generates docs and symbol search from types, and records every CI publish in a public cryptographic transparency log. Demo shows score rising from ~29% to 100% after adding docs, installs via existing package managers, and a publish from GitHub Actions flow with no local tokens, plus yank version and source‑mapped debugging.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:07npm registry problems
- 5:43Introducing JSR
- 7:51Publishing with TypeScript
- 11:42npm compatibility
- 15:33Live demo: JSR website
- 17:40Publish to JSR steps
- 23:01CLI authentication
- 27:38Using JSR packages
- 32:17JSR benefits
- 34:04Documentation generation and user experience
- 34:25Publish via GitHub Actions
- 37:39Summary
related talks
29mState of Deno
29mState of Deno
46mThe “Perfect” JS Library Tooling
41mThe Future of JavaScript Package Management
23mJSDocs: It's like TypeScript but without all that TypeScript
23mPublishing in JavaScript Ecosystem: How to Keep Everyone Happy?
05mHow we have built a Node.js Registry with React
32mThe "Perfect" Tooling Library