4d34684f1f
* fix: check for both bundleDependencies and bundledDependencies (#7411) update to code that didn't correctly check both bundleDependencies and bundledDependencies * fix: support boolean value for bundleDependencies (#7411) fix so that a 'true' value in the bundleDependencies field is correctly interpreted (as meaning all dependencies are bundled) close #7411 * fix: allow saving of boolean bundledDependencies values updates prior fix to allow saving booleans to bundledDependencies field. * fix: add test coverage for bundledDependencies fixes (#7411) add local tarball test and bundledDependencies=true test update existing tests to confirm that bundled dependencies aren't installed * fix: update registry-mock * docs: update changeset * fix: update bundleDependencies tests * Revert "fix: update registry-mock" This reverts commit0c4b7ede21. * Revert "Revert "fix: update registry-mock"" This reverts commit9828dfce91. * test: update integrities in test lockfiles * test: retry twice * test: move bundle deps test to separate file --------- Co-authored-by: Zoltan Kochan <z@kochan.io>
简体中文 | 日本語 | 한국어 | 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 env use.
- 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.
Gold Sponsors
|
|
|
|
|
Silver Sponsors
|
|
|
|
|
|
|
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:
Usage Trend
Backers
Thank you to all our backers! Become a backer
Contributors
This project exists thanks to all the people who contribute. Contribute.
