Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Error when installing yeoman #2813

Closed
ttback opened this Issue · 8 comments

6 participants

@ttback

Running npm install -g yeoman as instructed from get.yeoman.io.
It seems to think that node is 0.6.18 and npm is at 1.1.19, but my node is at v0.8.7

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

npm ERR! Error: No compatible version found: yeoman
npm ERR! No valid targets found.
npm ERR! Perhaps not compatible with your version of node?
npm ERR! at installTargetsError (/usr/lib/nodejs/npm/lib/cache.js:486:10)
npm ERR! at next_ (/usr/lib/nodejs/npm/lib/cache.js:436:17)
npm ERR! at next (/usr/lib/nodejs/npm/lib/cache.js:413:44)
npm ERR! at /usr/lib/nodejs/npm/lib/cache.js:406:5
npm ERR! at saved (/usr/lib/nodejs/npm/lib/utils/npm-registry-client/get.js:151:7)
npm ERR! at Object.oncomplete (/usr/lib/nodejs/graceful-fs/graceful-fs.js:230:7)
npm ERR! 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!
npm ERR! System Linux 2.6.18-274.17.1.0.1.el5xen
npm ERR! command "nodejs" "/usr/bin/npm" "install" "-g" "yeoman"
npm ERR! cwd /home/MY-ACCOUNT/setup
npm ERR! node -v v0.6.18
npm ERR! npm -v 1.1.19
npm ERR! message No compatible version found: yeoman
npm ERR! message No valid targets found.
npm ERR! message Perhaps not compatible with your version of node?
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/MY-ACCOUNT/setup/npm-debug.log
npm not ok

@mfncooper
Collaborator

Try node -v immediately before you run npm install -g yeoman and I'd bet it tells you v0.6.18. If you have v0.8.7, it's not on your path (or is later on your path), since v0.6.18 is what started npm.

@loldrup

I have npm version 1.1.4 and I have the exact same issue as OP.

@mfncooper
Collaborator

@loldrup npm 1.1.4 is verging on antique - you need to update. The current version is 1.1.63.

@jeremyworboys

I'm getting this same issue.

[...]
npm http 404 http://nodeload.github.com/yeoman/generators/tarball/3d709c61cd
npm ERR! fetch failed http://nodeload.github.com/yeoman/generators/tarball/3d709c61cd
npm ERR! Error: 404 Not Found
npm ERR!     at null.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/fetch.js:47:16)
npm ERR!     at EventEmitter.emit (events.js:126:20)
npm ERR!     at WriteStream.flush (fs.js:1517:12)
npm ERR!     at fs.close (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:90:5)
npm ERR!     at Object.oncomplete (fs.js:297: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 Darwin 12.2.1
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "yeoman"
npm ERR! cwd /Users/jeremy
npm ERR! node -v v0.8.14
npm ERR! npm -v 1.1.65
[...]
@da-v-id

Yeah, I'm getting that same issue too. If anyone could help, or at least point us in the right direction, that would be awesome.

@mfncooper
Collaborator

The yeoman package is currently completely broken. There is nothing that npm can do about that. You'll need to take the issue up with the authors of that package.

Here's how broken:

$ npm view yeoman dependencies
{ grunt: 'http://nodeload.github.com/gruntjs/grunt/tarball/0ba6d4b529',
  'yeoman-generators': 'http://nodeload.github.com/yeoman/generators/tarball/3d709c61cd',
  // complete list snipped for brevity
  'grunt-contrib-coffee': '~0.3.1' }

$ curl -I http://nodeload.github.com/gruntjs/grunt/tarball/0ba6d4b529
HTTP/1.1 404 Not Found
Server: nginx
Date: Sat, 03 Nov 2012 15:47:37 GMT
Connection: keep-alive

$ curl -I http://nodeload.github.com/yeoman/generators/tarball/3d709c61cd
HTTP/1.1 404 Not Found
Server: nginx
Date: Sat, 03 Nov 2012 15:48:14 GMT
Connection: keep-alive
@mfncooper mfncooper closed this
@da-v-id
@isaacs
Owner

Fixed by yeoman maintainers.

@isaacs isaacs reopened this
@isaacs isaacs closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.