Pointless? about npm-check-updates HOT 11 CLOSED

For now npm outdated is pretty enough !

from npm-check-updates.

Even in version 1.3.13 npm outdated won't show me newest versions if I have exact versions specified in my package.json

$ npm-check-updates
...
Dependency "express" could be updated to 3.4.4
Dependency "less" could be updated to 1.5.0
Dependency "moment" could be updated to 2.4.0
Dependency "nodemailer" could be updated to 0.5.5
Dependency "mocha" could be updated to 1.14.0
Dependency "should" could be updated to 2.0.2
Dependency "supertest" could be updated to 0.8.1
Dependency "xml-digester" could be updated to 0.0.5

$ npm outdated
...
[email protected] node_modules\mongodb current=1.3.19
[email protected] node_modules\underscore current=1.5.2
[email protected] node_modules\express current=3.4.0
[email protected] node_modules\nodemailer current=0.5.2
[email protected] node_modules\q current=0.9.7
[email protected] node_modules\moment current=2.2.1
[email protected] node_modules\less current=1.4.2

from npm-check-updates.

If you are using exact versions, doesnt that mean you want that exact version and dont care about updates?

from npm-check-updates.

No, I'm using exact versions because I know everything works 100% with them. From time to time I use npm-check-updates to check if there are newer versions available, then read their change-logs and carefully consider updating to exact new version.

from npm-check-updates.

did a quick test.
package.json file: "grunt-contrib-jshint": "0.6.0",

running npm outdated:
grunt-contrib-jshint node_modules/grunt-contrib-jshint current=0.6.0 wanted=0.6.0 latest=0.7.1

from npm-check-updates.

My npm doesn't show latest even though version is [email protected], strange.
Even npm install -g npm didn't help anything.

from npm-check-updates.

Ok, you're right. Latest is there (in 1.3.13) making this plugin kind of obsolete but still not that much.
npm-check-updates -g still works for globally installed modules, you can't do that with npm itself.

My problem was that:

npm install -g npm updates the version in modules folder: C:\Users\<user>\AppData\Roaming\npm\node_modules\npm

BUT In latest node version, npm is executed from here:
C:\Program Files\nodejs\node_modules\npm

I had to manually copy npm from first directory to second to make it work.

ping https://github.com/isaacs/npm/issues/1840 , @isaacs

from npm-check-updates.

with latest npm version you get the following update:

npm outdated --depth=0 --json
{
  "gulp-rename": {
    "current": "1.0.0",
    "wanted": "1.0.0",
    "latest": "1.1.0",
    "location": "node_modules\\gulp-rename"
  },
  "gulp-nodemon": {
    "current": "0.1.2",
    "wanted": "0.1.2",
    "latest": "1.0.0",
    "location": "node_modules\\gulp-nodemon"
  }
}

So basically showing you current version, wanted version (according to pacakge.json) and what's the latest version.

I do think that the default npm outdated command should use --depth=0 but that's another issue.

Does npm update [packagename]@latest work with versions outside your definitions?

from npm-check-updates.

For now, I find npm-check-updates output far clearer that npm outdated. Now internally, npm-check-updates could use npm outdated. That's another issue.

from npm-check-updates.

There's no other way I know of to actually upgrade packages to the latest version automatically.

from npm-check-updates.

Thanks for the feedback. This module was created before "npm outdated" was available. Personally I still prefer the npm-check-updates output so I'll continue to maintain it, also specifying --depth=0 for npm is annoying.

from npm-check-updates.