pnpm update

Aliases: up, upgrade

pnpm update updates packages to their latest version based on the specified range.

When used without arguments, updates all dependencies.

TL;DR

Selecting dependencies with patterns

You can use patterns to update specific dependencies.

Update all babel packages:

pnpm update "@babel/*"

Update all dependencies, except webpack:

pnpm update !webpack

Patterns may also be combined, so the next command will update all babel packages, except core:

pnpm update "@babel/*" !@babel/core

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 depth
pnpm --recursive update --depth 100
# update typescript to the latest version in every package
pnpm --recursive update typescript@latest

--latest, -L

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, -g

Update global packages.

--workspace

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

Show outdated dependencies and select which ones to update.

--filter <package_selector>

Read more about filtering.