mirror of
https://github.com/pnpm/pnpm.git
synced 2025-12-23 23:29:17 -05:00
69ebe38764
* fix: throw a frozen lockfile error when catalogs change * fix: work around lockfile mismatch when installing `__fixtures__` ``` > @ step1 /home/runner/work/pnpm/pnpm/__fixtures__ > node ../pnpm/dist/pnpm.mjs install -rf --frozen-lockfile --no-shared-workspace-lockfile --no-link-workspace-packages . | WARN using --force I sure hope you know what you are doing Scope: all 26 workspace projects circular | Progress: resolved 1, reused 0, downloaded 0, added 0 circular | +4 + fixture | Progress: resolved 1, reused 0, downloaded 0, added 0 fixture | +12 + fixture-with-no-pkg-name-and-no-version | Progress: resolved 1, reused 0, downloaded 0, added 0 fixture-with-no-pkg-name-and-no-version | +12 + fixture-with-no-pkg-version | Progress: resolved 1, reused 0, downloaded 0, added 0 fixture-with-no-pkg-version | +12 + circular | Progress: resolved 4, reused 0, downloaded 4, added 4, done fixture | Progress: resolved 12, reused 6, downloaded 6, added 12, done fixture-with-no-pkg-name-and-no-version | Progress: resolved 12, reused 0, downloaded 0, added 12, done fixture-with-no-pkg-version | Progress: resolved 12, reused 0, downloaded 0, added 12, done general | Progress: resolved 1, reused 0, downloaded 0, added 0 general | +13 + has-2-outdated-deps | Progress: resolved 1, reused 0, downloaded 0, added 0 has-2-outdated-deps | +2 + undefined /home/runner/work/pnpm/pnpm/__fixtures__/has-outdated-deps-using-catalog-protocol: ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Cannot proceed with the frozen installation. The current "catalogs" configuration doesn't match the value found in the lockfile Update your lockfile using "pnpm install --no-frozen-lockfile" ``` close #9369
简体中文 | 日本語 | 한국어 | 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.
Platinum Sponsors
|
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:
