outdated Verified current stable Not installed? Package Management

Outdated / Check Outdated Dev Dependencies

Check Outdated Dev Dependencies

Checks for outdated development dependencies in a PNPM project.

$
Terminal
pnpm outdated -D

When To Use

When preparing to upgrade dev dependencies in your project before a release.

Pro Tip

Utilize `--long` for guidance on what can be upgraded, facilitating decision-making.

Anatomy of Output

Understanding the result

Package Current Wanted Latest Location Header Row

Header indicating what each column represents.

eslint 7.21.0 7.22.0 8.0.0 /path/to/node_modules Example Outdated Dev Dependency

Detailing current, wanted, and latest versions for a specific package.

Troubleshooting

Common pitfalls

Error: No outdated dev dependencies found.

Solution: Ensure there are dev dependencies defined in your package.json.

Error: Command failed due to missing configuration files.

Solution: Verify if package.json and its structure are correctly set up.

Error: Permission denied while accessing node_modules.

Solution: Check your permissions and ownership of the node_modules directory.

Command Breakdown

What each part is doing

pnpm
Base Command
The executable that performs this operation. Here it runs Outdated before the shell applies any redirect operators.
-D
D| dev
The value supplied for D| dev.
-D
Command Option
Tool-specific option used by this command invocation.

Alternative Approaches

Comparable commands in other tools

Alternative package management tools for the same job.