Khải
22290afecb
`CopyPermissions` was a type alias: `std::fs::Permissions` off WASI, and a
bare `u32` on it, because WASI metadata omits the permission bits and the
host supplies the mode instead. Callers therefore wrote the same thing
twice, once per target:
#[cfg(unix)]
let permissions = Permissions::from_mode(0o755);
#[cfg(target_os = "wasi")]
let permissions = 0o755;
and a trait in `cmd-shim` had a parameter whose type changed with the
target, while two files aliased the one name over the other with
`use pnpm_fs::CopyPermissions as Permissions;`.
It is a newtype now, wrapping what each platform's own calls hand over:
the bits where a platform has them, the read-only attribute on Windows,
which is the whole of `fs::Permissions` there. The vocabulary is
`of_metadata` and `copy_permissions` to read, `from_mode` and `mode` for
the bits, `apply_to_file` and `apply_to_path` to write. The platform
difference lives in the one module, and the callers name one type.
`pack`'s archive writer shows it at its clearest: one arm wrote the mode
back through `fs::Permissions` and another through a free
`set_file_permissions`, and both are now one `from_mode(mode)
.apply_to_file(...)` call.
A WASI imitation of `fs::Permissions` was the alternative. It keeps two
distinct types, so the branching only moves: wherever std's own API wants
the real `fs::Permissions`, an imitation cannot be passed. Nor could it be
made interchangeable, since `PermissionsExt` does not exist on WASI. A
bits-only type was the other alternative, and Windows rules it out: the
read-only attribute is all `fs::Permissions` carries there, so POSIX bits
cannot represent what a copy preserves.
That retires two lint suppressions the divide forced, both of the form
`#[allow(clippy::trivially_copy_pass_by_ref, reason = "Shares the native
permissions signature")]`, which existed only because `u32` is `Copy`
and `Permissions` is not.
`mode` masks the file type off, where `PermissionsExt::mode` reports it.
Every reader of those bits tests or sets the low ones, so the masking
changes no result.
`apply_to_path` follows a final symlink off WASI and refuses one on WASI,
the divergence the two call sites it replaced already had. Its doc had
claimed it followed one everywhere.
简体中文 | 日本語 | 한국어 | 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.
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.