mirror of
https://github.com/pnpm/pnpm.git
synced 2026-03-26 19:12:12 -04:00
0b33718dbe
* refactor: merge @pnpm/fs.find-packages into @pnpm/workspace.projects-reader The find-packages package had only one production consumer (projects-reader). Inlining it removes a separate published package with minimal value as a standalone utility. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: sort devDependencies and add tsconfig reference for meta-updater Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: remove circular tsconfig reference Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: exclude circular tsconfig reference in meta-updater Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * refactor: move getConfig from cli/utils to pnpm CLI package getConfig and installConfigDepsAndLoadHooks were the only functions in cli/utils that pulled in heavy deps (env-installer, store.connection-manager, hooks.pnpmfile, default-reporter). Moving them to the pnpm CLI package (their only consumer) dramatically reduces the dependency weight of cli/utils, breaking the circular tsconfig reference chain that previously required fs.find-packages to be a separate package. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: sort imports Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
简体中文 | 日本語 | 한국어 | 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
|
|
|
|
|
|
|
⏱️ 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:
