karma problems while trying to set up an angular project

Question

I'm trying to set up an environment that supports angular/coffeescript/sass/jade.. and was told angular-curve does an excellent job.

I get stuck at this part: after cloning the repo and running npm install I get this error:

npm ERR! peerinvalid The package karma does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants karma@~0.9.4 || ~0.10
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9.3
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.11.14
npm ERR! peerinvalid Peer [email protected] wants karma@>=0.9

npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/abdullah/dev/js/sandbox/bayt
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.9
npm ERR! code EPEERINVALID
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/abdullah/dev/js/sandbox/bayt/npm-debug.log
npm ERR! not ok code 0

see the output of my npm ls here, and npm ls global returns empty.

Coming from a rails/bundler background, and reading that npm allows for nested dependencies (ie you can have 2 libraries having each one dependency in different versions) i don't see why/how this problem is happening. Help anyone?

Answer 1

Just change karma version in package.json to "karma": "^0.9.0" or "karma": ">=0.9.0" and make npm update

Update

Also try to update grunt-karma too. I just tried and it wasn't work with previous changes. So, as you mentioned: "grunt-karma": ">=0.5.0", "karma": ">=0.9.0", and npm update.

Actually i usually remove all versions from such outdated package files and do npm update, cause eventually you have to update them (kinda newbie thing perhaps, and not recommended). So, if previous doesn't help, you can try this. Last time i have only one small problem with newest versions.

Before that you can also type npm cache clean in console.