Zoltan Kochan
a7c94a905d
`TreeCtx`'s state (`packages`, `dependencies_tree`, `all_peer_dep_names`, `policy_violations`, `applied_patches`) was guarded by `tokio::sync::Mutex`. Every visit acquired 2-3 of them behind `.lock().await`, paying the async-mutex per-acquire overhead (registration, future polling, wake) on the resolve hot path. None of the critical sections hold the lock across an `.await` — they're short `HashMap` / `HashSet` inserts and `Vec::push`es. That's exactly the shape `std::sync::Mutex` is for. Switch the fields, remove the `.await`s, and route every acquire through a new `lock_recoverable` helper that mirrors the rest of the codebase's poisoning recovery (`build_modules.rs`, `pick_package.rs`, …): an unrelated panic shouldn't escalate into a hard install failure since the guarded values are plain collections with no invariants that survive a panic. Side effects: - `TreeCtx::snapshot` and `TreeCtx::resolved_versions` drop the `async` qualifier and their callers drop the `.await`. The closures they live in are still `async` (they await elsewhere), so the change is mechanical. - `update_preferred_versions_with_ctx` becomes sync along with `resolved_versions`. Tests: 50/50 in `pacquet-resolving-deps-resolver` pass. Clippy clean.
简体中文 | 日本語 | 한국어 | 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.
- 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:
