No compatible version found

[ghost]

When I want to install my app with the following package.json

{
    "name": "SLOTPLUS-API",
    "version": "1.0.1",
    "private": true,
    "scripts": {
    "start": "nodemon app.js"
},
    "dependencies": {
    "express": "*"
},

I got this error log:

npm ERR! Error: No compatible version found: inherits@'^2.0.1'
npm ERR! Valid install targets:
npm ERR! ["1.0.0","2.0.0","2.0.1"]
npm ERR!     at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:719:10)
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:638:10
npm ERR!     at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:133:7
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 2.6.32-431.el6.x86_64
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /home/crundadmin/test
npm ERR! node -v v0.10.15
npm ERR! npm -v 1.3.5
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/crundadmin/test/npm-debug.log
npm ERR! not ok code 0

I also test to specify the version like
"express": "3.5.1"
but it's the same

[timoxley]

@maxime-crunding This is related to #4587. Please update your version of npm with npm install -g npm and try again.

[ramonskie]

we have the same problem but the update did not work

EDIT: it works now a bit strange.
because i needed to run the update command several times

1. resulted in

npm http GET https://registry.npmjs.org/npm
npm http 304 https://registry.npmjs.org/npm
npm http GET https://registry.npmjs.org/npm/1.4.6
npm http 200 https://registry.npmjs.org/npm/1.4.6
npm http GET https://registry.npmjs.org/npm/-/npm-1.4.6.tgz
npm http 200 https://registry.npmjs.org/npm/-/npm-1.4.6.tgz
npm WARN package.json github-url-from-git@1.1.1 No repository field.
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires semver@'^2.2.1' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver,
npm WARN unmet dependency which is version 2.2.1

npm http GET https://registry.npmjs.org/npm
npm http 304 https://registry.npmjs.org/npm

3. no output
   and then the npm version was updated

[nnt]

Could you try new version of npm? That might help. I upgraded to version 1.4.4 and it worked fine.

[jimbol]

Updated npm and it worked just fine for me.

[burlakilia]

Thanks, it helped.

[timoxley]

@maxime-crunding bump

[syberkitten]

on windows: npm install -g npm
does not update the npm version.
Have: 1.2.32
after upgrade, the same!

Will try installing the Windows Binary (MSI) and see if it helps.

[FooBarWidget]

I had a similar problem. After upgrading to NPM 1.4.10, it went away.

[timoxley]

Closing. This is resolved by updating npm.

[nikoloza]

Updating NPM does not help for me.

[kenany]

@nikoloza Open a new issue with a link to your npm-debug.log uploaded to gist.github.com.

[nikoloza]

@kenany I think I made it workable by just updating all packages. I have other issue now, and I'll make one for that. Thanks

[daifee]

i got the same error. because i had reseted my registry, and the registry has not the package (saved in package.json by other people from other registry).

[dgreene1]

Off topic (I know, I'm sorry), but is there a way to have 'npm install' output a warning if the npm version is too low?

It would be great to prevent issues like the above. For instance, I can confirm that the fix was @timoxley 's suggested answer of updating the npm version. So if npm install first checked to see if you had the minimum version for this particular package.json... then it would prevent lots of unnecessary roadblocks for new team members.

Any suggestions?

[kenany]

@dgreene1 There's https://docs.npmjs.com/files/package.json#engines, but I forgot if it currently emits a warning or not.