Urgent.News

What's breaking now, across thousands of outlets.

Tech

JavaScript installer pnpm recast in Rust because ECMAScript can't keep up

Fully backward-compatible upgrade promises zero-friction speedup for monorepo wranglers.

JavaScript installer pnpm recast in Rust because ECMAScript can't keep up

JavaScript package manager pnpm has undergone a significant transformation, transitioning from JavaScript to Rust in a bid to enhance performance. This marked change, introduced in version 12, has been credited with reducing installation times by up to 90 percent. Maintainer Zoltan Kochan assured users that this update would not be disruptive, as the old commands, flags, settings, and lockfile format remain intact, and comprehensive documentation covers both versions.

A new Rust-based registry server, pnpr, further boosted performance, cutting installation time down to just 3.37 seconds when used as the backend. The new core binary, currently 65.9 percent Rust and 33.5 percent TypeScript, eliminates much of the overhead that comes from routing filesystem work through Node.js. The project's benchmarking against other package managers like Bun and Yarn revealed impressive results, with pnpm slashing installation times by up to 90 percent in certain scenarios.

Initially created by Developer Rico Sta. Cruz in 2016 as a more efficient alternative to npm, pnpm gained popularity for its content-addressable storage, which downloads libraries only once for multiple applications. This Rust rewrite of pnpm has been met with mixed reactions, with some praising its speed, while others lament the loss of familiarity.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at theregister.com →

More in Tech

What Kubernetes Health Checks Actually Guarantee

Kubernetes health checks tell you whether a workload satisfies the narrow condition the probe was designed to test. They do not tell you whether the business objective that workload exists to serve…

  • Kubernetes health checks verify process conditions, not business objectives.
  • Probes check process response, not business logic execution.
  • Misconception exists that passing signals mean business goals achieved.

More from Friday 4 September →