Zoltan Kochan
07839df5c3
* docs: move website documentation into the pnpm repository * docs: keep v11 and v12 documentation beside their implementations * docs(pnpr): keep registry documentation beside its implementation * ci: classify product documentation as documentation changes * test: cover product documentation in Rust CI exclusions * ci: isolate documentation publishing and support manual sync * test: make dependency status fixture timestamps deterministic
2.0 KiB
id, title
| id | title |
|---|---|
| remove | pnpm remove |
Aliases: rm, uninstall, un
Removes packages from node_modules and from the project's package.json.
Since v11.28.0, pnpm remove runs the project's own preuninstall, uninstall, and postuninstall scripts. See Uninstall scripts.
Options
--recursive, -r
When used inside a workspace, removes a dependency (or dependencies) from every workspace package.
When used not inside a workspace, removes a dependency (or dependencies) from every package found in subdirectories.
Since v11.28.0, the command fails before any package.json is modified if a requested dependency is absent from every selected project. The check respects --save-prod, --save-dev, and --save-optional.
--global, -g
Remove a global package.
--save-dev, -D
Only remove the dependency from devDependencies.
--save-optional, -O
Only remove the dependency from optionalDependencies.
--save-prod, -P
Only remove the dependency from dependencies.
--unsafe-perm
Added in: v11.26.0
Accepted for compatibility with pnpm install; see unsafePerm.
Supply-chain policy flags
Added in: v11.26.0
pnpm remove accepts the same policy overrides as pnpm install and pnpm add: --trust-lockfile, --no-trust-lockfile, --trust-policy, --trust-policy-exclude, and --trust-policy-ignore-after.
Removing a package rewrites the lockfile, so pnpm remove verifies the whole lockfile against the active policies the way pnpm install does, not only the entries of the package being removed. --trust-lockfile skips that pass entirely.