npm outdated [[<@scope>/]<pkg> ...]
This command will check the registry to see if any (or, specific) installed packages are currently outdated.
In the output:
wantedis the maximum version of the package that satisfies the semver range specified in
package.json. If there's no available semver range (i.e. you're running
npm outdated --global, or the package isn't included in
wantedshows the currently-installed version.
latestis the version of the package tagged as latest in the registry. Running
npm publishwith no special configuration will publish the package with a dist-tag of
latest. This may or may not be the maximum version of the package, or the most-recently published version of the package, depending on how the package's developer manages the latest dist-tag.
locationis where in the dependency tree the package is located. Note that
npm outdateddefaults to a depth of 0, so unless you override that, you'll always be seeing only top-level dependencies that are outdated.
package type(when using
-l) tells you whether this package is a
devDependency. Packages not included in
package.jsonare always marked
$ npm outdatedPackage Current Wanted Latest Locationglob 5.0.15 5.0.15 6.0.1 test-outdated-outputnothingness 0.0.3 git git test-outdated-outputnpm 3.5.1 3.5.2 3.5.1 test-outdated-outputlocal-dev 0.0.3 linked linked test-outdated-outputonce 1.3.2 1.3.3 1.3.3 test-outdated-output
A few things to note:
^5, which prevents npm from installing
glob@6, which is outside the semver range.
npm updatehave to fetch Git repos to check. This is why currently doing a reinstall of a Git dependency always forces a new clone and install.
email@example.com marked as "wanted", but "latest" is
firstname.lastname@example.org npm uses dist-tags to manage its
npm updatewill install the newest version, but
npm install npm(with no semver range) will install whatever's tagged as
onceis just plain out of date. Reinstalling
node_modulesfrom scratch or running
npm updatewill bring it up to spec.
Show information in JSON format.
Show extended information.
Show parseable output instead of tree view.
Check packages in the global install prefix instead of in the current project.
Max depth for checking dependency tree.
Last modified November 17, 2016 Found a typo? Send a pull request!