Software Version / Package Tools

npm Package Version Checker

Check which published version your package.json spec would install, and whether a newer version exists outside your range.

Enter a dependency spec from package.json and paste the package's published versions - the tool shows the version npm would pick and whether an update needs a spec change.

Package name

Version spec from package.json

Published versions

Paste the output of this command (JSON array, or one version per line). This tool does not contact the npm registry itself.

Treat prereleases as candidates (--include-prerelease)

More Software Version / Package Tools

View all 9

Version Increment Generator Composer Version Constraint Helper Version Comparator Python Requirements Version Helper SemVer Validator Dependency Version Comparator Version Range Calculator Package Name Validator

This works entirely from the versions you paste - it never contacts the npm registry, so it also works for private registries.

What Is the npm Package Version Checker?

It answers the question npm outdated answers for a single dependency: given the spec in your package.json (such as ^4.17.15), which published version is wanted, and what is the latest? It also recognises specs that are not version ranges at all - dist-tags, Git URLs, local paths, workspace references and npm: aliases.

When to Use It

To see what a fresh install (without a lockfile) would resolve to.
To find out whether you are missing a major release because of a caret range.
To debug an ETARGET "no matching version" error.

How to Use It

Enter the package name and its spec from package.json.
Run the shown command, e.g. npm view lodash versions --json, and paste its output.
Click Check Version.

Example

Spec ^4.17.15 with published versions 4.17.15-4.17.21 and 5.0.0-beta.1: wanted is 4.17.21, latest stable is 4.17.21, and the 5.0.0 beta is ignored because prereleases are not candidates by default.

Understanding the Result

Wanted - the highest published version your spec allows.
Latest stable - the highest non-prerelease version in your list.
If latest is outside your range, the tool says whether that is a major, minor or patch jump.

Limitations

This tool does not fetch data from npm. It does not know dist-tags, deprecations or your lockfile: npm prefers the version tagged latest when it satisfies the range, and a lockfile pins the installed version until you update. To explore the range syntax in depth, use the Version Range Calculator; to check a package name, use the Package Name Validator.

Frequently Asked Questions

Run npm view <package> versions --json in a terminal and paste the output. It also works with private registries your npm is configured for.

Wanted is the highest version your package.json range allows. Latest is the newest stable release. If they differ, updating to latest requires changing your range.

No. It works only with the versions you paste, in your browser.