npm outdated and npm update doesn't work

Question

I want to check if my modules are Latest

i do: sudo npm outdated

and I have this results

Package Current Wanted Latest Location oauth 0.9.9 0.9.9 0.9.10 twit > oauth require-all 0.0.3 0.0.3 0.0.8 mysql > require-all bignumber.js 1.0.1 1.0.1 1.3.0 mysql > bignumber.js request 2.27.0 2.27.0 2.30.0 facebook-chat > node-xmpp > node-xmpp-client > request through 2.2.7 2.2.7 2.3.4 facebook-chat > node-xmpp > brfs > through

then i do this:sudo npm update but if I repeat sudo npm outdated i have the same results... also if I do for example Info:

Package Current Wanted Latest Location oauth 0.9.9 0.9.9 0.9.10 twit > oauth

Then Update

sudo npm update oauth

Then

sudo npm outdated oauth

My Result:

Package Current Wanted Latest Location oauth 0.9.9 0.9.9 0.9.10 twit > oauth

Have you put specific package versions in your package.json file (e.g. ~0.11.8 instead of *)? I doubt that NPM update your packages if dependencies are too strict. — Cédric Belin
– Cédric Belin, Commented Dec 22, 2013 at 2:15

Jonathan Lonowski · Accepted Answer · 2013-12-22 04:15:30Z

Your project is actually as up-to-date as it can be currently.

NPM won't simply install the Latest version of a package unless that version is also Wanted.

The resulting field 'wanted' shows the latest version according to the version specified in the package.json, [...]

And, for each that you listed, the Wanted and Current versions already match.

Package Current Wanted ... oauth 0.9.9 0.9.9 ... require-all 0.0.3 0.0.3 ... bignumber.js 1.0.1 1.0.1 ... request 2.27.0 2.27.0 ... through 2.2.7 2.2.7 ...

An attempt to force oauth to its current Latest of 0.9.10, for example, would actually be considered invalid as twit has 0.9.9 listed exactly:

"dependencies": { "oauth": "0.9.9" },

$ npm ls ... └─┬ [email protected] └── [email protected] invalid npm ERR! invalid: [email protected] ...\node_modules\twit\node_modules\oauth

thanks for reply ! twit use oauth 0.9.9, but this dependence is on 0.9.10 version, which is not updated until Twit does not require it .. force oauth to 0.9.10 version may cause errors...is this want you mean ?
@Barno Yeah. twit will have to update its "dependencies" to allow [email protected] to be installed under it. Though, since twit is an open-source project, the author(s) may be welcome to a pull request with that update, provided all of its tests still pass.

Narendra Sagadevan · Accepted Answer · 2017-04-21 18:03:35Z

Check your package.json may be your packages or there there. try to install package with --save and try it will work

example : npm install [email protected] --save now try npm outdated

Collectives™ on Stack Overflow

npm outdated and npm update doesn't work

2 Answers 2

4 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

Comments

Linked

Related