search

hubotio / generator-hubot

Hubot generator for Yeoman
MIT License
156 stars 83 forks source link

phantomjs does not satisfy its siblings' peerDependencies requirements! #7

Closed enzolutions closed 9 years ago

enzolutions commented 9 years ago

After trying to install the generator for hubot I got the following error

$ npm install -g generator-hubot
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "generator-hubot"
npm ERR! node v0.10.32
npm ERR! npm  v2.1.4
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package phantomjs does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer mocha-phantomjs@3.4.1 wants phantomjs@~1.9.1

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/enzo/www/hubot/npm-debug.log

and this is the log

17442 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/read-installed/read-installed.js:251:14
17443 verbose cwd /Users/enzo/www/hubot
17444 error Darwin 14.0.0
17445 error argv "node" "/usr/local/bin/npm" "install" "-g" "generator-hubot"
17446 error node v0.10.32
17447 error npm  v2.1.4
17448 error code EPEERINVALID
17449 error peerinvalid The package phantomjs does not satisfy its siblings' peerDependencies requirements!
17449 error peerinvalid Peer mocha-phantomjs@3.4.1 wants phantomjs@~1.9.1
technicalpickles commented 9 years ago

That is really bizarre, because we don't use mocha-phantom.js as far as I know. Maybe it's a problem with a dependency's dependency?

technicalpickles commented 9 years ago

I tried testing this on npm 1.3.11 (what I had installed), 2.1.8 (the latest), and 2.1.4 (what you reported) and wasn't able to reproduce. I also had a slightly different node (0.10.21 vs your 0.10.32), but I wouldn't have thought that would make a difference.

Could you perhaps include more of your npm-debug.log? It looks like it was a bit truncated. Maybe remove it so a new one is started?

technicalpickles commented 9 years ago

Another thought I had... what directory were you running it in? Was it in a directory that had a package.json with mocha-phantomjs?

I'm going to close for now, but happy to look into it if you can help give some more details.