Zoltan Kochan
652dcc802b
Nine files under `crates/cli/tests/suite/` carried a file-level `#![cfg(unix)]`, and the two `pnpm`-differential tests in `root.rs` and `bin.rs` carried a Windows `ignore`, so none of them ever compiled or ran on the Windows CI job. Four of the gates blamed "program not found" on spawning the external `pnpm`. That dates from pacquet's own CI, which installed pnpm through npm as a `pnpm.cmd` shim: Windows resolves a bare program name against `.exe` alone, so the spawn failed. The workflows have installed pnpm through `pnpm/setup` since 2026-05, and that action downloads pnpm's native `pnpm.exe`, which resolves. Nothing in those four files is unix-specific beyond the spawn. The other gates were harness details rather than platform behavior: - `repeat_install.rs` compared inode numbers to tell a file the install reused from one it replaced. It now takes a hard link as a witness and compares with `same_file`, which answers the same question on both platforms. - `multiple_importers.rs` asserted the executable bit on a linked bin. `bundled_dependencies.rs` already had a helper that checks the bit on Unix and the `.cmd` / `.ps1` launchers on Windows; it moves to the shared test utils and both files call it. - `pnpx_alias.rs` copied the binary under a name with no `.exe` suffix. - `ignore_workspace.rs` ran `pwd`, and `pipeline_watch.rs` ran `mkdir -p` and `cp`, from a package script. Both now use `node -e`, as `pipeline_cache.rs` already did. - `pipeline_cargo_cache.rs` ran its built probe binary by a path with no `.exe` suffix. Five files stay gated, each with a comment saying why: `interrupt.rs` sends POSIX signals, `run_recursive.rs` and `exec_recursive.rs` put POSIX shell bodies in nearly every package script, and `global_virtual_store.rs` and `hoisted_node_linker.rs` assert layouts shaped around symlinks. Un-gating those is the remainder of pnpm/pnpm#15089. Related to pnpm/pnpm#15089.
简体中文 | 日本語 | 한국어 | Italiano | Português Brasileiro
Fast, disk space efficient package manager:
- Fast. Up to 2x faster than the alternatives (see benchmark).
- Efficient. Files inside
node_modulesare linked from a single content-addressable storage. - Great for monorepos.
- Strict. A package can access only dependencies that are specified in its
package.json. - Deterministic. Has a lockfile called
pnpm-lock.yaml. - Works as a Node.js version manager. See pnpm runtime.
- Works everywhere. Supports Windows, Linux, and macOS.
- Battle-tested. Used in production by teams of all sizes since 2016.
- Experimental Rust port. Includes pacquet, an experimental port of the CLI written in Rust.
- See the full feature comparison with npm and Yarn.
To quote the Rush team:
Microsoft uses pnpm in Rush repos with hundreds of projects and hundreds of PRs per day, and we’ve found it to be very fast and reliable.
Platinum Sponsors
|
|
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
Silver Sponsors
|
|
|
|
|
|
|
|
|
| ⏱️ Time.now |
Support this project by becoming a sponsor.
Background
pnpm uses a content-addressable filesystem to store all files from all module directories on a disk. When using npm, if you have 100 projects using lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be stored in a content-addressable storage, so:
- If you depend on different versions of lodash, only the files that differ are added to the store.
If lodash has 100 files, and a new version has a change only in one of those files,
pnpm updatewill only add 1 new file to the storage. - All the files are saved in a single place on the disk. When packages are installed, their files are linked from that single place consuming no additional disk space. Linking is performed using either hard-links or reflinks (copy-on-write).
As a result, you save gigabytes of space on your disk and you have a lot faster installations!
If you'd like more details about the unique node_modules structure that pnpm creates and
why it works fine with the Node.js ecosystem, read this small article: Flat node_modules is not the only way.
💖 Like this project? Let people know with a tweet
Getting Started
Benchmark
pnpm is up to 2x faster than npm and Yarn classic. See all benchmarks here.
Benchmarks on an app with lots of dependencies:
License
MIT, except the pnpr/ directory, which is source-available under the PolyForm Shield License 1.0.0.