Article: pnpm’s core team has pushed an alpha build of version 12 that runs as a native Rust binary, promising install times that can be an order of magnitude faster than the current Node-based version. The change matters because CI jobs will finish much faster.

Why the rewrite matters

pnpm already distinguishes itself from npm and Yarn by using a content-addressable store and a strict node_modules layout. Yet every command still starts a Node.js process, incurring a fixed startup cost before any file work begins. By moving the heavy-lifting code to Rust, the team eliminates that bootstrap step and taps Rust’s ability to run many file operations in parallel, something a single JavaScript thread can’t match.

The numbers behind the claim

Benchmarks supplied by the pnpm team show dramatic drops across three common scenarios:

  • Warm install (repeat run): from 381 ms to 12 ms.
  • No-cache install: from 460 ms to 40 ms.
  • Clean install (full dependency tree): from 6.5 s to 2.2 s.

A 30× improvement on warm installs translates directly into faster CI jobs and tighter developer feedback loops.

What stays the same

The rewrite is a port, not a redesign. All existing flags, lockfile format, and the strict node_modules structure remain untouched. Projects can continue to run pnpm install exactly as before; the only visible difference should be speed. Because the public API does not change, the migration path is intended to be painless.

How to try it now

The transition is staged. In the current v11 line, developers can opt into the experimental Rust backend by enabling the “pacquet” backend flag. In v12, the Rust engine becomes the default for fetching packages and linking them into the workspace. The alpha release is published under the next-12 tag; it is not recommended for production use yet, but anyone curious can install it with a single command and begin testing.

Risks and counter-points

Even with a clean API surface, an alpha binary carries the usual caveats: limited testing and potential edge-case regressions.

The broader trend

pnpm’s move mirrors a growing pattern among front-end tooling. Projects such as Biome and Oxc have also rewritten core components in compiled languages to shave milliseconds off developer workflows.