32d4d3f1f0
* feat(cli): port the `root` command to pacquet Add `pacquet root`, ported from pnpm11/pnpm/src/cmd/root.ts. Prints `<dir>/node_modules` built from the canonicalized `--dir`. It hardcodes the `node_modules` leaf and deliberately does not read `config.modules_dir`: pnpm's handler ignores a configured modules-dir, and pacquet re-anchors `config.modules_dir` to the workspace root inside a workspace, whereas pnpm's `root` uses `config.dir` (the cwd). Anchoring on `--dir` keeps parity in both cases. `--global` / `-g` is rejected with a "not supported yet" error: pacquet has no global packages directory yet, deferred to a shared follow-up that also unblocks `bin -g`. Related to pnpm/pnpm#11633. * fix(cli): gate `root` differential test on Windows and type its `--global` error The `root_matches_pnpm_from_a_workspace_subdir` differential test spawns the real `pnpm`, which on Windows is a `pnpm.cmd` shim that `std::process::Command` cannot resolve via `PATHEXT` ("program not found"). Gate it with `#[cfg_attr(target_os = "windows", ignore)]`, matching the `cfg(unix)` gating in `pnpm_compatibility` and `hoist`. The other three `root` tests spawn only `pacquet` and keep running on Windows. Replace the bare `miette::miette!` rejection of `pacquet root --global` with a typed `RootError::GlobalUnsupported` diagnostic (code `pacquet_cli::root_global_unsupported`), mirroring `runtime`'s `GlobalUnsupported`, so the refusal carries a stable error code.
简体中文 | 日本語 | 한국어 | 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.