Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPM 2.6.9 Not valid #508

Closed
setphen1 opened this issue Sep 22, 2017 · 2 comments
Closed

NPM 2.6.9 Not valid #508

setphen1 opened this issue Sep 22, 2017 · 2 comments

Comments

@setphen1
Copy link

setphen1 commented Sep 22, 2017

I'm currently unable to get anything with this package as a dependency to install after the latest update to 2.6.9. The npm repo page says that there is a 2.6.9 package available, but the npm install does not list this and fails.

$ npm install
npm ERR! Darwin 15.6.0
npm ERR! argv "/Users/skennedy/.nvm/versions/node/v6.10.2/bin/node" "/Users/skennedy/.nvm/versions/node/v6.10.2/bin/npm" "install"
npm ERR! node v6.10.2
npm ERR! npm  v3.10.10
npm ERR! code ETARGET

npm ERR! notarget No compatible version found: debug@2.6.9
npm ERR! notarget Valid install targets:
npm ERR! notarget 3.0.1, 3.0.0, 2.6.8, 2.6.7, 2.6.6, 2.6.5, 2.6.4, 2.6.3, 2.6.2, 2.6.1, 2.6.0, 2.5.2, 2.5.1, 2.5.0, 2.4.5, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4.0, 2.3.3, 2.3.2, 2.3.1, 2.3.0, 2.2.0, 2.1.3, 2.1.2, 2.1.1, 2.1.0, 2.0.0, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 0.8.1, 0.8.0, 0.7.4, 0.7.3, 0.7.2, 0.7.1, 0.7.0, 0.6.0, 0.5.0, 0.4.1, 0.4.0, 0.3.0, 0.2.0, 0.1.0, 0.0.1
npm ERR! notarget 
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of 'body-parser'
npm ERR! notarget 
@TooTallNate
Copy link
Contributor

TooTallNate commented Sep 22, 2017

It works for me:

$ npm install debug@2

+ debug@2.6.9
added 2 packages in 1.152s

Are you sure you're not behind a caching npm proxy or something like that?

@setphen1
Copy link
Author

Yes, this points to an artifactory caching problem I think. I only had others behind the proxy test. I will pursue internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants