search

eliias / grunt-docco

Uses docco to generate nice HTML docs out of your annotated source.
MIT License
4 stars 5 forks source link

Error: No compatible version found: docco@'jashkenas/docco#d6fd45c164d490b72d9e2e22698fae55d64e1dec' #4

Closed ghost closed 11 years ago

ghost commented 11 years ago

It seems like some people are having problem running npm install grunt-docco2. I personally could not reproduce the problem on mac os, but a co-worker got

npm http GET https://registry.npmjs.org/grunt-docco2
npm http 304 https://registry.npmjs.org/grunt-docco2
npm http GET https://registry.npmjs.org/docco
npm http 304 https://registry.npmjs.org/docco
npm ERR! Error: No compatible version found: docco@'jashkenas/docco#d6fd45c164d490b72d9e2e22698fae55d64e1dec'
npm ERR! Valid install targets:
npm ERR! ["0.2.0","0.3.0","0.4.0","0.5.0","0.6.0","0.6.1","0.6.2"]
npm ERR!     at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:553:10)
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:477:15
npm ERR!     at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:218:7
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>

on his Windows 7 machine with npm --version 1.3.11. Also, I found this gist describing the exact same issue.

eliias commented 11 years ago

Have the same problem here on a Jenkins build machine. The problem is I need to target a special commit as 0.6.2 version of docco is quite old (9 months or so). I will look into this today and push a fix as soon as I know exactly what is going on.

eliias commented 11 years ago

I have fixed it with 0.1.4. At least on my Jenkins server it is working as expected. Would it be possible for your colleague to try again and can you let me know the results?

ghost commented 11 years ago

Seems to be fixed with 0.1.5.