1NPM-OUTDATED(1)                                                NPM-OUTDATED(1)
2
3
4

NAME

6       npm-outdated - Check for outdated packages
7
8   Synopsis
9         npm outdated [[<@scope>/]<pkg> ...]
10
11   Description
12       This  command  will  check  the  registry  to see if any (or, specific)
13       installed packages are currently outdated.
14
15       In the output:
16
17       · wanted is the maximum version  of  the  package  that  satisfies  the
18         semver  range  specified  in  package.json.  If  there's no available
19         semver range (i.e.  you're running  npm  outdated  --global,  or  the
20         package  isn't  included in package.json), then wanted shows the cur‐
21         rently-installed version.
22
23       · latest is the version of the package tagged as  latest  in  the  reg‐
24         istry.   Running  npm publish with no special configuration will pub‐
25         lish the package with a dist-tag of latest. This may or  may  not  be
26         the  maximum  version  of the package, or the most-recently published
27         version of the package, depending on how the package's developer man‐
28         ages the latest dist-tag npm-dist-tag.
29
30       · location is where in the dependency tree the package is located. Note
31         that npm outdated defaults to a depth of 0, so  unless  you  override
32         that,  you'll  always  be seeing only top-level dependencies that are
33         outdated.
34
35       · package type (when using --long / -l) tells you whether this  package
36         is  a  dependency  or a devDependency. Packages not included in pack‐
37         age.json are always marked dependencies.
38
39       · homepage (when using --long / -l) is the homepage value contained  in
40         the package's package.json
41
42       · Red  means there's a newer version matching your semver requirements,
43         so you should update now.
44
45       · Yellow indicates that there's  a  newer  version  above  your  semver
46         requirements  (usually  new  major, or new 0.x minor) so proceed with
47         caution.
48
49
50   An example
51         $ npm outdated
52         Package      Current   Wanted   Latest  Location
53         glob          5.0.15   5.0.15    6.0.1  test-outdated-output
54         nothingness    0.0.3      git      git  test-outdated-output
55         npm            3.5.1    3.5.2    3.5.1  test-outdated-output
56         local-dev      0.0.3   linked   linked  test-outdated-output
57         once           1.3.2    1.3.3    1.3.3  test-outdated-output
58
59       With these dependencies:
60
61         {
62           "glob": "^5.0.15",
63           "nothingness": "github:othiym23/nothingness#master",
64           "npm": "^3.5.1",
65           "once": "^1.3.1"
66         }
67
68       A few things to note:
69
70       · glob requires ^5, which prevents npm from installing glob@6, which is
71         outside the semver range.
72
73       · Git  dependencies  will always be reinstalled, because of how they're
74         specified.  The installed committish  might  satisfy  the  dependency
75         specifier  (if  it's  something  immutable, like a commit SHA), or it
76         might not, so npm outdated and npm update have to fetch Git repos  to
77         check.  This  is  why currently doing a reinstall of a Git dependency
78         always forces a new clone and install.
79
80       · npm@3.5.2 is marked as "wanted", but "latest"  is  npm@3.5.1  because
81         npm  uses  dist-tags  to manage its latest and next release channels.
82         npm update will install the newest version, but npm install npm (with
83         no semver range) will install whatever's tagged as latest.
84
85       · once  is  just  plain  out  of  date.  Reinstalling node_modules from
86         scratch or running npm update will bring it up to spec.
87
88
89   Configuration
90   json
91       · Default: false
92
93       · Type: Boolean
94
95
96       Show information in JSON format.
97
98   long
99       · Default: false
100
101       · Type: Boolean
102
103
104       Show extended information.
105
106   parseable
107       · Default: false
108
109       · Type: Boolean
110
111
112       Show parseable output instead of tree view.
113
114   global
115       · Default: false
116
117       · Type: Boolean
118
119
120       Check packages in the global install prefix instead of in  the  current
121       project.
122
123   depth
124       · Default: 0
125
126       · Type: Int
127
128
129       Max depth for checking dependency tree.
130
131   See Also
132       · npm help update
133
134       · npm help dist-tag
135
136       · npm help registry
137
138       · npm help folders
139
140
141
142
143                                  March 2020                   NPM-OUTDATED(1)