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) in‐
13       stalled packages are currently outdated.
14
15       By default, only the direct dependencies of the root project and direct
16       dependencies  of  your  configured  workspaces are shown.  Use --all to
17       find all outdated meta-dependencies as well.
18
19       In the output:
20
21       • wanted is the maximum version  of  the  package  that  satisfies  the
22         semver  range  specified  in  package.json.  If  there's no available
23         semver range (i.e.  you're running  npm  outdated  --global,  or  the
24         package  isn't  included in package.json), then wanted shows the cur‐
25         rently-installed version.
26
27       • latest is the version of the package tagged as  latest  in  the  reg‐
28         istry.   Running  npm publish with no special configuration will pub‐
29         lish the package with a dist-tag of latest. This may or  may  not  be
30         the  maximum  version  of the package, or the most-recently published
31         version of the package, depending on how the package's developer man‐
32         ages the latest npm help dist-tag.
33
34       • location is where in the physical tree the package is located.
35
36       • depended by shows which package depends on the displayed dependency
37
38       • package  type (when using --long / -l) tells you whether this package
39         is a dependency or a dev/peer/optional dependency. Packages  not  in‐
40         cluded in package.json are always marked dependencies.
41
42       • homepage  (when using --long / -l) is the homepage value contained in
43         the package's packument
44
45       • Red means there's a newer version matching your semver  requirements,
46         so you should update now.
47
48       • Yellow  indicates  that there's a newer version above your semver re‐
49         quirements (usually new major, or new 0.x minor) so proceed with cau‐
50         tion.
51
52
53   An example
54         $ npm outdated
55         Package      Current   Wanted   Latest  Location                  Depended by
56         glob          5.0.15   5.0.15    6.0.1  node_modules/glob         dependent-package-name
57         nothingness    0.0.3      git      git  node_modules/nothingness  dependent-package-name
58         npm            3.5.1    3.5.2    3.5.1  node_modules/npm          dependent-package-name
59         local-dev      0.0.3   linked   linked  local-dev                 dependent-package-name
60         once           1.3.2    1.3.3    1.3.3  node_modules/once         dependent-package-name
61
62       With these dependencies:
63
64         {
65           "glob": "^5.0.15",
66           "nothingness": "github:othiym23/nothingness#master",
67           "npm": "^3.5.1",
68           "once": "^1.3.1"
69         }
70
71       A few things to note:
72
73       • glob requires ^5, which prevents npm from installing glob@6, which is
74         outside the semver range.
75
76       • Git dependencies will always be reinstalled, because of  how  they're
77         specified.   The  installed  committish  might satisfy the dependency
78         specifier (if it's something immutable, like a  commit  SHA),  or  it
79         might  not, so npm outdated and npm update have to fetch Git repos to
80         check.  This is why currently doing a reinstall of a  Git  dependency
81         always forces a new clone and install.
82
83       • npm@3.5.2  is  marked  as "wanted", but "latest" is npm@3.5.1 because
84         npm uses dist-tags to manage its latest and  next  release  channels.
85         npm update will install the newest version, but npm install npm (with
86         no semver range) will install whatever's tagged as latest.
87
88       • once is just  plain  out  of  date.  Reinstalling  node_modules  from
89         scratch or running npm update will bring it up to spec.
90
91
92   Configuration
93       <!--  AUTOGENERATED  CONFIG  DESCRIPTIONS  START --> <!-- automatically
94       generated, do not edit manually --> <!--  see  lib/utils/config/defini‐
95       tions.js -->
96
97   all
98       • Default: false
99
100       • Type: Boolean
101
102
103       When  running npm outdated and npm ls, setting --all will show all out‐
104       dated or installed packages, rather than only those  directly  depended
105       upon by the current project.  <!-- automatically generated, do not edit
106       manually --> <!-- see lib/utils/config/definitions.js -->
107
108
109   json
110       • Default: false
111
112       • Type: Boolean
113
114
115       Whether or not to output JSON data, rather than the normal output.
116
117       • In npm pkg set it enables parsing set values with JSON.parse() before
118         saving them to your package.json.
119
120
121       Not  supported  by  all npm commands.  <!-- automatically generated, do
122       not edit manually --> <!-- see lib/utils/config/definitions.js -->
123
124
125   long
126       • Default: false
127
128       • Type: Boolean
129
130
131       Show extended information in ls, search, and help-search.   <!--  auto‐
132       matically  generated,  do not edit manually --> <!-- see lib/utils/con‐
133       fig/definitions.js -->
134
135
136   parseable
137       • Default: false
138
139       • Type: Boolean
140
141
142       Output parseable results from commands that write to  standard  output.
143       For npm search, this will be tab-separated table format.  <!-- automat‐
144       ically generated, do not edit  manually  -->  <!--  see  lib/utils/con‐
145       fig/definitions.js -->
146
147
148   global
149       • Default: false
150
151       • Type: Boolean
152
153
154       Operates in "global" mode, so that packages are installed into the pre‐
155       fix folder instead of the current working directory. See npm help fold‐
156       ers for more on the differences in behavior.
157
158       • packages are installed into the {prefix}/lib/node_modules folder, in‐
159         stead of the current working directory.
160
161       • bin files are linked to {prefix}/bin
162
163       • man pages are linked to {prefix}/share/man
164
165       <!-- automatically  generated,  do  not  edit  manually  -->  <!--  see
166       lib/utils/config/definitions.js -->
167
168
169   workspace
170       • Default:
171
172       • Type: String (can be set multiple times)
173
174
175       Enable running a command in the context of the configured workspaces of
176       the current project while filtering by running only the workspaces  de‐
177       fined by this configuration option.
178
179       Valid values for the workspace config are either:
180
181       • Workspace names
182
183       • Path to a workspace directory
184
185       • Path to a parent workspace directory (will result to selecting all of
186         the nested workspaces)
187
188
189       When set for the npm init command, this may be set to the folder  of  a
190       workspace  which does not yet exist, to create the folder and set it up
191       as a brand new workspace within the project.
192
193       This value is not exported to  the  environment  for  child  processes.
194       <!--  automatically  generated,  do  not  edit  manually  -->  <!-- see
195       lib/utils/config/definitions.js -->
196
197       <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
198
199
200   See Also
201       • npm help update
202
203       • npm help dist-tag
204
205       • npm help registry
206
207       • npm help folders
208
209       • npm help workspaces
210
211
212
213
214                                 October 2021                  NPM-OUTDATED(1)