@cryptotaxi247 / documentation-1
Code Commits Issues Pulls Sessions CI/CD
@reggi/path-to-regexp
@reggi/path-to-regexp dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2 dependabot/npm_and_yarn/main/eslint-10.4.0 dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0 dependabot/npm_and_yarn/main/proc-log-7.0.0 dependabot/npm_and_yarn/npm_and_yarn-826852524d dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2 deprecate-totp-2fa dhei/classic-tokens gat-bypass-2fa-docs jpg619/fix-accessibility-content-flow jpg619/version-bump-tar-2 kartykp/gat-bypass-2fa-docs kartykp/upgrade-path-to-regex main maitxn/version-bump-tar patch-1 reggi/cache-based-on-version reggi/dev-engines reggi/fix-transform-prettier reggi/overrides update-search-sensitivity
mdx 114 lines 4.29 KB
Raw
1 ---
2 title: npm-outdated
3 section: 1
4 description: Check for outdated packages
5 github_repo: npm/cli
6 github_branch: release/v6
7 github_path: docs/content/commands/npm-outdated.md
8 redirect_from:
9 - /cli-documentation/v6/cli-commands/npm-outdated
10 - /cli-documentation/v6/cli-commands/outdated
11 - /cli-documentation/v6/commands/npm-outdated
12 - /cli-documentation/v6/commands/outdated
13 - /cli-documentation/v6/npm-outdated
14 - /cli-documentation/v6/outdated
15 - /cli/v6/cli-commands/npm-outdated
16 - /cli/v6/cli-commands/outdated
17 - /cli/v6/commands/outdated
18 - /cli/v6/npm-outdated
19 - /cli/v6/outdated
20 ---
21
22 ### Synopsis
23
24 ```bash
25 npm outdated [[<@scope>/]<pkg> ...]
26 ```
27
28 ### Description
29
30 This command will check the registry to see if any (or, specific) installed packages are currently outdated.
31
32 In the output:
33
34 - `wanted` is 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 `package.json`), then `wanted` shows the currently-installed version.
35 - `latest` is the version of the package tagged as latest in the registry. Running `npm publish` with 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](npm-dist-tag).
36 - `location` is where in the dependency tree the package is located. Note that `npm outdated` defaults to a depth of 0, so unless you override that, you'll always be seeing only top-level dependencies that are outdated.
37 - `package type` (when using `--long` / `-l`) tells you whether this package is a `dependency` or a `devDependency`. Packages not included in `package.json` are always marked `dependencies`.
38 - `homepage` (when using `--long` / `-l`) is the `homepage` value contained in the package's `package.json`
39 - Red means there's a newer version matching your semver requirements, so you should update now.
40 - Yellow indicates that there's a newer version above your semver requirements (usually new major, or new 0.x minor) so proceed with caution.
41
42 ### An example
43
44 ```bash
45 $ npm outdated
46 Package Current Wanted Latest Location
47 glob 5.0.15 5.0.15 6.0.1 test-outdated-output
48 nothingness 0.0.3 git git test-outdated-output
49 npm 3.5.1 3.5.2 3.5.1 test-outdated-output
50 local-dev 0.0.3 linked linked test-outdated-output
51 once 1.3.2 1.3.3 1.3.3 test-outdated-output
52 ```
53
54 With these `dependencies`:
55
56 ```json
57 {
58 "glob": "^5.0.15",
59 "nothingness": "github:othiym23/nothingness#master",
60 "npm": "^3.5.1",
61 "once": "^1.3.1"
62 }
63 ```
64
65 A few things to note:
66
67 - `glob` requires `^5`, which prevents npm from installing `glob@6`, which is outside the semver range.
68 - Git dependencies will always be reinstalled, because of how they're specified. The installed committish might satisfy the dependency specifier (if it's something immutable, like a commit SHA), or it might not, so `npm outdated` and `npm update` have to fetch Git repos to check. This is why currently doing a reinstall of a Git dependency always forces a new clone and install.
69 - `npm@3.5.2` is marked as "wanted", but "latest" is `npm@3.5.1` because npm uses dist-tags to manage its `latest` and `next` release channels. `npm update` will install the _newest_ version, but `npm install npm` (with no semver range) will install whatever's tagged as `latest`.
70 - `once` is just plain out of date. Reinstalling `node_modules` from scratch or running `npm update` will bring it up to spec.
71
72 ### Configuration
73
74 #### json
75
76 - Default: false
77 - Type: Boolean
78
79 Show information in JSON format.
80
81 #### long
82
83 - Default: false
84 - Type: Boolean
85
86 Show extended information.
87
88 #### parseable
89
90 - Default: false
91 - Type: Boolean
92
93 Show parseable output instead of tree view.
94
95 #### global
96
97 - Default: false
98 - Type: Boolean
99
100 Check packages in the global install prefix instead of in the current project.
101
102 #### depth
103
104 - Default: 0
105 - Type: Int
106
107 Max depth for checking dependency tree.
108
109 ### See Also
110
111 - [npm update](/cli/v6/commands/npm-update)
112 - [npm dist-tag](/cli/v6/commands/npm-dist-tag)
113 - [npm registry](/cli/v6/using-npm/registry)
114 - [npm folders](/cli/v6/configuring-npm/folders)