pnpm update
Aliases: up
pnpm update updates packages to their latest version based on the specified
range.
When used without arguments, updates all dependencies. You can use patterns to update specific dependencies.
TL;DR#
| Command | Meaning |
|---|---|
pnpm up | Updates all dependencies, adhering to ranges specified in package.json |
pnpm up --latest | Updates all dependencies, ignoring ranges specified in package.json |
pnpm up foo@2 | Updates foo to the latest version on v2 |
pnpm up "@babel/*" | Updates all dependencies under the @babel scope |
Options#
--recursive, -r#
Concurrently runs update in all subdirectories with a package.json (excluding
node_modules).
Usage examples:
pnpm --recursive update# updates all packages up to 100 subdirectories in depthpnpm --recursive update --depth 100# update typescript to the latest version in every packagepnpm --recursive update typescript@latest--latest, -L#
Added in: v3.2.0
Ignores the version range specified in package.json. Instead, the version specified by the latest tag will be used (potentially upgrading the packages across major versions).
--global#
Update global packages.
--workspace#
Added in: v4.4.0
Tries to link all packages from the workspace. Versions are updated to match the versions of packages inside the workspace.
If specific packages are updated, the command will fail if any of the updated
dependencies are not found inside the workspace. For instance, the following
command fails if express is not a workspace package:
pnpm up -r --workspace express.
--prod, -P#
Only update packages in dependencies and optionalDependencies.
--dev, -D#
Only update packages in devDependencies.
--no-optional#
Don't update packages in optionalDependencies.
--interactive, -i#
Added in: v4.8.0
Show outdated dependencies and select which ones to update.