* feat(cli/config)!: breaking changes * refactor(test): remove `deepNullProto` and reuse `getOutputString` * feat(cli/config/list): censor protected settings * test: censorship of protected settings * docs(changeset): censorship of protected settings * fix: eslint * feat(config)!: exclude non-option from `rawConfig` * fix: eslint * refactor: move default registries to builtin (#9886) * feat(config)!: filter rc settings * feat(config): don't exclude non-options This reverts commita79f72dbfb. * feat(cli/config/get)!: print array as json * test: fix * docs(changeset): correct * test: fix * feat(cli/config)!: only kebabize option fields (wip) * chore(git): revert the implementation This reverts commit529f9bdd47. * test: restore This reverts commitd8191e0ed8. * feat(cli/config)!: only kebabize option fields (wip) * feat: use `types` instead * feat(cli/config/get)!: only kebabize rc fields * test: add * test: non-rc kebab-case keys * test: correct * docs(changeset): correct * docs(changeset): style * docs(changeset): correct * test: only kebabize rc fields * fix: import path * fix: eslint * fix: `isCamelCase` * feat(cli/config/set)!: forbid unknown rc fields * test: fix existing test * test: refuse unsupported rc settings * feat: hint * feat(cli/config/set)!: refuse kebab-case workspace-specific settings * feat(config)!: ignore non-camelCase from `pnpm-workspace.yaml` * test: config get * test: config list * refactor: extract shared code into its own package * test: `isCamelCase` * feat(cli/config/list)!: consistent naming cases * refactor: make it more reusable * feat(cli/config/get)!: consistent naming cases * feat(cli/config/get): censor protected settings * test: `get ''` should be the same as `list` * docs(test): quotation marks * refactor: remove unnecessary `test.each` * docs(changeset): case changes * test: unknown keys * docs(changeset): correct * docs(changeset): non camelCase from `pnpm-workspace.yaml` * fix: eslint * docs(changeset): correct terminology * docs(changeset): clarify * feat!: do not load non-auth and non-registry * fix: implementation * test: no hidden settings * fix: eslint * fix: do not drop default values * test: fix * test: remove irrelevant tests * test: fix (wip) * fix: auth * test: skip an inapplicable test * test: temporary skip a test * test: fix 'respects testPattern' * test: fix 'respects changedFilesIgnorePattern' * test: fix 'changedFilesIgnorePattern is respected' * test: rename a test * test: fix `package-lock=false` * feat: exception for `managePackageManagerVersions` * test: `managePackageManagerVersions: false` * test: fix (wip) * test: workaround * fix: default `optional` to `true` * fix: `filter` on `pnpm-workspace.yaml` * test: fix * test: disable ones that no longer apply * chore(git): revert incorrect change * fix: `filter` on `pnpm-workspace.yaml` (#10127) * fix: `filter` on `pnpm-workspace.yaml` * docs: changeset * fix: actual fix * fix: don't set default on config * docs(readme): correct a package description * fix: typo * test: fix * test: use a field that wouldn't be ignored * test: replace some `.npmrc` with `pnpm-workspace.yaml` * docs(changeset): less awkward wordings * docs(changeset): correction
简体中文 | 日本語 | 한국어 | 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: