Article: pnpm’s core team is rolling out a Rust-based rewrite for v12, slashing warm install times from 381 ms to 12 ms and clean installs from 6.5 s to 2.2 s. The speed boost matters most to developers who run packages in continuous-integration (CI) pipelines, where every second adds up.

Why the rewrite matters now

pnpm already beats many rivals on speed, but it runs on Node.js, which forces a startup cost each time the command launches. That cost shows up as a noticeable pause in CI jobs that repeatedly fetch and link dependencies. By moving the heavy lifting into a native Rust binary—codenamed pacquet—the team eliminates the Node.js bootstrap and lets Rust handle massive file-system churn with a single thread.

The rewrite is a port, not a redesign. All flags, lockfile formats, and the familiar node_modules layout stay exactly the same, so existing scripts and workflows need no changes. In v11 you can already opt into the pacquet backend; v12 makes it the default for fetching and linking.

Measurable performance gains

Benchmarks supplied by the maintainers show:

  • Warm install (repeat run with cache): 381 ms → 12 ms, a 30-fold improvement.
  • Clean install (no cache): 6.5 s → 2.2 s, cutting more than half the time.

Risks and trade-offs

The Rust engine is still in alpha. The team advises against using v12 in production until it graduates out of the pre-release stage.

How to try it today

Developers can test the new backend by running pnpm self-update next-12, which pulls the latest pre-release binary. The command swaps the JavaScript engine for the Rust one without altering the project’s pnpm-lock.yaml or node_modules layout. Teams that want to evaluate the impact on their CI pipelines should spin up a disposable runner, enable the pacquet backend, and compare build times against the current setup.

The broader trend

pnpm’s move mirrors a wave of tooling migrations toward compiled languages. Projects such as Biome, Oxc, and Deno have all rebuilt performance-critical components in Rust or Go to shave latency from developer workflows.

What to watch next

  • Stability milestones: Monitoring releases will tell when it’s safe for production use.
  • Feature parity: Users should keep an eye on the changelog for gaps.

The bottom line: pnpm’s Rust rewrite turns an already fast package manager into a practically instantaneous one for repeat installs, and it cuts more than half the time for fresh installs. For teams that spend minutes on dependency resolution every night, the upgrade promises a measurable reduction in CI costs without demanding a workflow overhaul.