search

webcomponents / webcomponents.github.io

WebComponents.org is where community-members document Web Components best practices
http://webcomponents.org
733 stars 126 forks source link

Getting a npm install error #160

Closed agektmr closed 9 years ago

agektmr commented 9 years ago

Newly cloned repository with following command returns an error. This causes building docpad failure.

npm install
...
npm WARN deprecated tap-consumer@0.0.1: this is merged into the 'tap' module now
npm WARN deprecated tap-results@0.0.2: this is merged into the 'tap' module now
npm ERR! Darwin 13.4.0
npm ERR! argv "node" "/Users/agektmr/.nodebrew/current/bin/npm" "install"
npm ERR! node v0.11.13
npm ERR! npm  v2.1.4
npm ERR! code ETARGET

npm ERR! notarget No compatible version found: eco@'>=1.1.0 <1.2.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.0.0","1.0.1","1.0.2","1.0.3","1.1.0-rc-1","1.1.0-rc-2","1.1.0-rc-3"]
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.
addyosmani commented 9 years ago

What version of npm do you have? npm -v?

agektmr commented 9 years ago

2.1.4

addyosmani commented 9 years ago

We've had a ton of issues around npm 2.x over on Web Starter Kit and Yeoman. For this site, I ended up downgrading to an earlier version e.g 1.4. @zenorocha have you run into any issues here?

zenorocha commented 9 years ago

I was able to simulate the same problem here and by updating docpad-plugin-eco it worked.

Not this case, but one tip for the future though is to run a stable version of node @agektmr (0.10 instead of 0.11).

agektmr commented 9 years ago

That is a great advice, thanks @zenorocha . The site is running without problem with node 0.10.32.