Zoltan Kochan
fc56dc12ec
Pin dylint.toml to the perfectionist revision that ships too_many_local_bindings, configure it at max_bindings = 12 with test code exempt, and keep it disabled until the remaining production sites are refactored. Give one install's phases a shared InstallContext: the config, install root, requester prefix, slot layout, node linker, allow-builds policy, bin-link options and import-method counter were declared again on every phase struct and threaded again by every caller. A phase borrows the context instead. The skip set stays a parameter of its own because phases mutate it between one another. Borrow a lockfile's packages and snapshots as one LockfileEntries value everywhere they were passed as two, and derive the link phase's and the frozen install's maps from the lockfile they already hold, so a caller cannot pair one lockfile's entries with another's maps. LockfileEntries::of_previous_install owns the --force rule that was an inline conditional at the frozen path's call site. Build InstallPackageBySnapshot once per install and pass each snapshot to run, which is what makes run_cold_batch extractable. Name the phases that were inline blocks: run_cold_batch, fetch_verified (which owns the rule that a fetch error must not surface before the verification verdict), run_on_disk_phases, requires_build_by_key. Name the (layout, hoisted-paths) pair as PkgRoots. Related to pnpm/pnpm#14562.
简体中文 | 日本語 | 한국어 | 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.