Check for outdated npm dependencies and update them with npm outdated and npm update
domain: docs.npmjs.com · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Run `npm outdated` at the package root to list direct dependencies and workspace deps whose installed version is behind the registry.
Read the columns: `Current` (installed), `Wanted` (max version matching the semver range in package.json), `Latest` (the version tagged fastest/latest in the registry, which may exceed your range).
Red rows mean a newer version satisfies your semver range (safe to update); yellow rows are above the range (typically a new major — updating requires a manual range change).
Run `npm update` to bring packages up to their `Wanted` versions, respecting your semver ranges, and update the lockfile.
Use `npm outdated --all` to include transitive/meta-dependencies beyond direct deps; add `--long`/`-l` to see dependency type and homepage, `--json` or `--parseable` for scriptable output.
For a major upgrade, edit the range in package.json (e.g. ^1 to ^2) then run npm install, and review breaking changes first.
Known gotchas
`Latest` reflects the release dist-tag, which is not necessarily the newest published version (projects use next/beta tags).
Git-managed dependencies are always reinstalled because npm must re-clone to check the committed commit.
npm update never bumps across a semver-major boundary unless you change the range in package.json.
npm outdated only checks direct deps by default — use --all for the full tree.
Give your agent this knowledge — and 16,900+ more routes
One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?