Updates

pnpm 11.2.2 adds experimental Rust install engine pacquet

pnpm 11.2.2 opens the door to pacquet, an experimental Rust install engine preview, while fixing the flag and lockfile bugs that surfaced on first contact.

Nina Kowalski··2 min read
Published
Listen to this article0:00 min
Share this article:
pnpm 11.2.2 adds experimental Rust install engine pacquet
Source: opengraph.githubassets.com

pnpm 11.2.2 pushed its Rust install experiment into users’ hands with pacquet, an opt-in preview aimed squarely at the part of the workflow that can make or break trust: materializing an install without breaking flags, lockfiles, or config parity. The setup is intentionally explicit. Add @pnpm/pacquet to configDependencies in pnpm-workspace.yaml, or run pnpm add @pnpm/pacquet config, and pnpm writes the change into pnpm-workspace.yaml and pnpm-lock.yaml for you to commit.

The split is sharp. pnpm still owns dependency resolution and writes the lockfile first; pacquet then fetches and imports from that freshly written lockfile. In 11.2.2, pnpm also started forwarding install-time CLI flags to pacquet’s install subcommand, including prod, dev, no-optional, node-linker, offline, and prefer-offline. That matters because the early preview had already exposed rough edges in real use, and this release directly patches one of them: pnpm up, pnpm add, and pnpm remove no longer fail with pacquet_package_manager::outdated_lockfile after pnpm passes ignore-manifest-check so pacquet does not trip its frozen-lockfile check against the pre-mutation package.json.

AI-generated illustration
AI-generated illustration

The rollout lands in the middle of a bigger transition that pnpm has been telegraphing for weeks. Its benchmark page, last updated May 18, 2026, says pnpm v12 will use a new installation engine written in Rust. The standalone pacquet repository was archived by its owner on May 14, 2026 and marked read-only, as the work moved into the main pnpm repository. In the roadmap discussion, pnpm describes pacquet as replacing fetching and linking only, with pnpm continuing to create the lockfile, and says that change alone is expected to make pnpm at least twice as fast in most scenarios.

The first feedback loop is already visible. One open issue says pacquet’s config reader misses pnpm’s global config.yaml and PNPM_CONFIG_* environment variables, a reminder that a fast path still has to meet the sprawling configuration habits of real projects. pnpm 11.2.2 is not the finish line for the Rust engine story; it is the first public test of whether pacquet can carry the install stage without dropping the behavior users already rely on.

Know something we missed? Have a correction or additional information?

Submit a Tip

Never miss a story.

Get Rust Programming updates weekly. The top stories delivered to your inbox.

Free forever · Unsubscribe anytime

Discussion

More Rust Programming News