Zoltan Kochan
78cf081f97
A pnpmfile that defines `hooks.importPackage` now gets a warning saying the hook is deprecated and will be removed in the next major version. The hook lets a pnpmfile take over writing a package into node_modules. It is a poor fit for where both stacks are heading: - Defining it drops the installation off the worker-thread importer entirely (`store/controller/src/storeController/index.ts`), and `store/create-cafs-store/src/index.ts` shows it also bypasses `pkgImportMethod` -- including the `willBeBuilt -> clone-or-copy` rule, so a hook that hardlinks corrupts the store once the package is built. - Porting it to the Rust CLI would put a JS callback on the hottest phase of the install, behind the single sequential Node worker that serves pnpmfile hooks, carrying the whole filesMap per package. It would also hand user JS the invariants `import_indexed_dir` owns: exclusive-mkdir ownership claiming for shared slots, marker-based repair, and the macOS quarantine sweep. - A GitHub-wide code search finds no pnpmfile using it outside copies of the documentation page, except one dev-server tool that only needs to know where a package landed and to force an import method. The warning points at pnpm/pnpm#14101 so anyone who does depend on the hook can say so before it is removed. Related to pnpm/pnpm#14101.
简体中文 | 日本語 | 한국어 | 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.