1 npm-outdated(1) -- Check for outdated packages
2 ==============================================
6 npm outdated [<name> [<name> ...]]
10 This command will check the registry to see if any (or, specific) installed
11 packages are currently outdated.
15 * `wanted` is the maximum version of the package that satisfies the semver
16 range specified in `package.json`. If there's no available semver range (i.e.
17 you're running `npm outdated --global`, or the package isn't included in
18 `package.json`), then `wanted` shows the currently-installed version.
19 * `latest` is the version of the package tagged as latest in the registry.
20 Running `npm publish` with no special configuration will publish the package
21 with a dist-tag of `latest`. This may or may not be the maximum version of
22 the package, or the most-recently published version of the package, depending
23 on how the package's developer manages the latest dist-tag(1).
24 * `location` is where in the dependency tree the package is located. Note that
25 `npm outdated` defaults to a depth of 0, so unless you override that, you'll
26 always be seeing only top-level dependencies that are outdated.
27 * `package type` (when using `--long` / `-l`) tells you whether this package is
28 a `dependency` or a `devDependency`. Packages not included in `package.json`
29 are always marked `dependencies`.
35 Package Current Wanted Latest Location
36 glob 5.0.15 5.0.15 6.0.1 test-outdated-output
37 nothingness 0.0.3 git git test-outdated-output
38 npm 3.5.1 3.5.2 3.5.1 test-outdated-output
39 local-dev 0.0.3 linked linked test-outdated-output
40 once 1.3.2 1.3.3 1.3.3 test-outdated-output
43 With these `dependencies`:
47 "nothingness": "github:othiym23/nothingness#master",
55 * `glob` requires `^5`, which prevents npm from installing `glob@6`, which is
56 outside the semver range.
57 * Git dependencies will always be reinstalled, because of how they're specified.
58 The installed committish might satisfy the dependency specifier (if it's
59 something immutable, like a commit SHA), or it might not, so `npm outdated` and
60 `npm update` have to fetch Git repos to check. This is why currently doing a
61 reinstall of a Git dependency always forces a new clone and install.
62 * `npm@3.5.2` is marked as "wanted", but "latest" is `npm@3.5.1` because npm
63 uses dist-tags to manage its `latest` and `next` release channels. `npm update`
64 will install the _newest_ version, but `npm install npm` (with no semver range)
65 will install whatever's tagged as `latest`.
66 * `once` is just plain out of date. Reinstalling `node_modules` from scratch or
67 running `npm update` will bring it up to spec.
76 Show information in JSON format.
83 Show extended information.
90 Show parseable output instead of tree view.
97 Check packages in the global install prefix instead of in the current
105 Max depth for checking dependency tree.