Zoltan Kochan
faa2606a8b
The Node.js addon (`pnpm-napi`) embeds the Rust engine as a cdylib loaded dynamically by Node.js. Rayon is statically linked into the cdylib and uses Rayon's global thread pool for parallel operations (such as workspace discovery, link phase clonefile/hardlinks, and store operations). Previously, the Rayon global pool sizing policy was defined only in `pnpm-cli`, meaning the Node.js addon defaulted to Rayon's unconstrained core-count pool sizing (which can spin up excessive worker threads on high-core machines and ignores container quota limits). This change: 1. Moves the sizing policy and initialization logic (`configure_rayon_pool`, `rayon_pool_size`, `RAYON_THREADS_PER_CORE`, `MIN_RAYON_THREADS`, `MAX_RAYON_THREADS`) into `pnpm-package-manager`. 2. Uses `std::sync::Once` for idempotent initialization across multiple calls and tests within the same process. 3. Configures the pool lazily when Node.js addon entry points (`install()`, `rebuild()`, `get_peer_dependency_issues()`, etc.) are called (deliberately avoiding `module_init` to prevent deadlocking with dynamic loader locks during `dlopen`). 4. Adds unit tests validating the sizing bounds and idempotence. Closes https://github.com/pnpm/tasks/issues/54
简体中文 | 日本語 | 한국어 | 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.