JavaScript installer pnpm recast in Rust because ECMAScript can't keep up
- ID
- 21453
- Status
- summarized
- Published
- 04 Sep 2026, 8:22 PM
- Fetched
- 04 Sep 2026, 8:41 PM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/devops/2026/09/04/javascript-installer-pnpm-recast-in-rust-because-ecmascript-cant-keep-up/5294394
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 7.5
- Created
- 04 Sep 2026, 8:41 PM
- Tags
- Audience
- developersvibe_coders
What happened
pnpm v12 has been rewritten in Rust (65.9% Rust, 33.5% TypeScript), cutting uncached install times from 8.22s (pnpm 11) to 5.19s, and to 3.37s when paired with a new Rust registry server called pnpr. The upgrade is fully backward-compatible: commands, flags, settings, and lockfile format from v11 carry over unchanged.
Why it matters
If you run monorepos or CI pipelines where npm install is a bottleneck, switching to pnpm 12 is a near-zero-risk drop-in upgrade that could cut install times dramatically. The Rust rewrite also signals that Node.js-based tooling is hitting performance ceilings that only native code can break.
Discussion angle
Is the JS ecosystem's slow migration to Rust/Go cores (pnpm, Bun, SWC, Turbopack) a sign that ECMAScript itself is the bottleneck, and what does that mean for devs who only know JavaScript?