Zoltan KochanandClaude Fable 5.1
46125ed2e2
Item 14 of pnpm/pnpm#14945, the placement half. Every Python project pnpm installed grew a `.pnpm/python-envs/` directory of generations beside its `.venv` link, so airflow's 141 projects got 141 generation directories where the repository maintains three environments. Generations now live under `<store>/python-envs/<project>/`, one directory per project named by the short hash of its canonical path, and `.venv` is the only thing left in the project: an absolute link to the generation the project currently runs. Publication is unchanged, an atomic symlink rename in the project directory, and so is rollback, which republishes the previous link. The link is a symlink or junction, so the store and the project need not share a filesystem. Where they do, the clone and hardlink methods of `packageImportMethod` now always have the environment on the store's filesystem. A `.venv` is managed when it links to a generation directory of any project directory in the store, not only this project's, so a project that moves keeps its environment rather than being refused as unmanaged. A link into the project's own `.pnpm/python-envs`, where 12.4 published environments, is managed too, so an upgrade relinks it on the next install and leaves the old generations for the user to delete. A link whose target is gone is replaced: the store can now be removed without the project, and a link to nothing protects nothing. Under frozenStore, which promises that nothing under the store is written, generations stay beside the project in the 12.4 layout, with its real-directory checks. A link to any other directory, or a `.venv` that is a real directory, is refused as before. The checks that the project's `.pnpm` is a real directory go away with the directory: an install no longer writes into the project's `.pnpm` at all. On Windows the link holds the absolute target through the new `pnpm_fs::force_absolute_symlink_dir`. The existing helper writes true symlinks relative to the link, which node_modules relies on and which a link into a store elsewhere on the disk cannot survive a move with. Generation collection stays open, as `pnpm/plans/PYTHON_SPIKE.md` records; a stale generation is now in the store rather than in the project. Closes pnpm/pnpm#15014. Co-authored-by: Claude Fable 5.1 <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 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.