See all outdated dependencies in a project at a glance without manually checking each package's changelog.
Update only patch and minor versions across a project while deliberately skipping major version bumps that may break things.
Interactively pick which packages to upgrade one at a time, skipping dependencies you know will cause compatibility problems.
npm-check-updates is a command-line tool that looks at your project's package.json file and tells you which dependencies have newer versions available. When you run it, it shows a list of packages and the version you're pinned to versus the latest version that exists. It does not install anything by itself, it only shows you what's out of date and, when you ask it to, rewrites the version numbers in your package.json. You then run your normal package manager install command to pull down the updated packages. The tool respects the version range notation you already use. If a dependency is listed as allowing any version starting with 17, and version 18 is now the latest, it updates that line to allow any version starting with 18. It does not flatten or remove the range style you chose, it just moves the number forward. It works with npm, yarn, pnpm, deno, and bun. There is an interactive mode that lets you look through the list of outdated packages and choose which ones to actually upgrade. Major version bumps are shown in red to signal that they may include breaking changes. Minor updates appear in cyan, and patch updates appear in green. You can filter by package name or use a pattern to include or exclude specific packages, which is useful when you want to update everything except one particular dependency that you know will cause problems. You can also control how aggressively the tool upgrades. By default it targets the latest stable version, but you can limit it to only patch releases, or only patch and minor releases, if you want to avoid major version jumps. There is a cooldown option that skips packages published very recently, which reduces the risk of pulling in a newly released package that turns out to have problems. Configuration lives in a .ncurc file that can sit next to your package.json or in your home directory, so you can set your preferences once and reuse them across projects. The full README is longer than what was shown.
← raineorshine on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.