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 install: grunt does not satisfy its siblings' peerDependencies requirements #431

Closed
RocAlayo opened this issue Aug 9, 2014 · 20 comments

Comments

@RocAlayo
Copy link

RocAlayo commented Aug 9, 2014

I just created a new app and npm install doesn't succeed installing all the dependencies, I get this:

npm ERR! peerinvalid The package grunt does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@>=0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.2
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.2
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.0
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1
npm ERR! peerinvalid Peer [email protected] wants grunt@^0.4.0

Before creating the app I updated all the packages in NPM so when I check my version of GruntJS I get this:

$ npm -g list grunt
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/insight requires chalk@'^0.5.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/chalk,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/update-notifier requires chalk@'^0.5.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/chalk,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/yo requires yeoman-generator@'^0.17.1' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/yeoman-generator,
npm WARN unmet dependency which is version 0.17.2
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/extname requires map-key@'^0.1.1' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/map-key,
npm WARN unmet dependency which is version 0.1.4
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/generator-ng-component/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/extname requires map-key@'^0.1.1' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/generator-ng-component/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/map-key,
npm WARN unmet dependency which is version 0.1.4
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/yo/node_modules/update-notifier requires chalk@'^0.5.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/generator-angular-fullstack/node_modules/yo/node_modules/chalk,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /usr/local/lib/node_modules/gulp/node_modules/gulp-util requires chalk@'^0.5.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/gulp/node_modules/chalk,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /usr/local/lib/node_modules/yo/node_modules/update-notifier requires chalk@'^0.5.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/yo/node_modules/chalk,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /usr/local/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/extname requires map-key@'^0.1.1' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/download/node_modules/decompress/node_modules/map-key,
npm WARN unmet dependency which is version 0.1.4
/usr/local/lib
└── [email protected]

I supose I have a problem with all that npm WARN unmet dependency but I don't know how to fix it.

@JaKXz
Copy link
Collaborator

JaKXz commented Aug 9, 2014

Try npm cache clean and try install again.

@RocAlayo
Copy link
Author

RocAlayo commented Aug 9, 2014

Same as before. Although tasks of grunt seem to work correctly, I tried grunt serve and grunt build and they work fine.

@JaKXz
Copy link
Collaborator

JaKXz commented Aug 9, 2014

Strange. Try npm install -g npm yo bower

Otherwise stackoverflow would be your best bet.

@RocAlayo
Copy link
Author

RocAlayo commented Aug 9, 2014

Now I have a new set of errors but I realize that this errors doesn't have anything to do with the generator so thanks for your help I will search in stackoverflow.

@JaKXz JaKXz closed this as completed Aug 9, 2014
@meeDamian
Copy link
Contributor

Yeah, I'm getting the same error all of the time. No idea what's the cause, but I'm quite sure it isn't this generator. I'd be glad to hear a solution, if someone has it, though :)

@RocAlayo
Copy link
Author

RocAlayo commented Aug 9, 2014

I finally fixed it by uninstalling node, npm and all the configurations that they saved in my mac and reinstalling it afterwards. Now is working fine. This post in stackoverflow helped me to find all the pieces that node leave in the system. :)

@sebastien-worms
Copy link

FYI : I had the same problem and resolved it by running a :

brew update
brew upgrade
npm remove -g grunt

and removing my Grunt, Bower local directories.
and re-installing it all.
Didn't have the time to find precisely where it came from.

Hope it helps.

@droidenator
Copy link

I also had this problem and the following worked for me

npm update -g

I'm assuming that uninstalling everything and then re-installing is probably accomplishing something along the same lines.

@glencoates
Copy link

@droidenator worked for me too ... thanks for that

@uxdxdev
Copy link

uxdxdev commented Jun 7, 2016

npm update -g worked for me, thanks.

@jared-cxz
Copy link

I got similar error when I run grunt install on Bamboo. By adding "grunt": "~0.4.5" into the dependencies section in package.json, it was fixed.

@arielcalcano
Copy link

both, npm cache clean and npm update -g worked for me. Thanks.

@bplv112
Copy link

bplv112 commented Jan 7, 2017

This is the best solution.

npm cache clean
npm update -g

@victorsj1
Copy link

None of these solutions worked for me. Still the same crap.

@cozyartz
Copy link

I'm having this issue running imageoptim. I haven't been able to figure it out after trying everything mentioned above.

@victorsj1
Copy link

This is getting frustrating because absolutely NOTHING is working. Why on earth was this garbage pushed out!? :<

@blee19
Copy link

blee19 commented Jan 18, 2017

Something that worked for me was running:

npm install grunt@~0.4.0

@victorsj1
Copy link

victorsj1 commented Jan 18, 2017 via email

@DanWallaceAdslot
Copy link

I had to
npm remove grunt
npm install grunt@~1.0.1
If I didn't specify the version with the ~, it wouldn't work

@fiazmr
Copy link

fiazmr commented Jul 23, 2018

I changed grunt-sass version inside package.json to ^3.0.0 but failed then with ^2.0.0 it worked

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

No branches or pull requests