generator-ionicjs shasum check failed

[martinclsn]

> npm install -g generator-ionicjs
info trying registry request attempt 1 at 23:11:37
http GET https://registry.npmjs.org/generator-ionicjs
http 304 https://registry.npmjs.org/generator-ionicjs
npm http GET https://registry.npmjs.org/generator-ionicjs/-/generator-ionicjs-0.2.5.tgz
npm http 200 https://registry.npmjs.org/generator-ionicjs/-/generator-ionicjs-0.2.5.tgz
npm ERR! Error: shasum check failed for /var/folders/0z/cc6w_vgn4bvgfknllmkp0xy40000gn/T/npm-950-rVN2gqdE/1397423498197-0.25426107505336404/tmp.tgz
npm ERR! Expected: 9855a928dc7d9792778316ea7664624fe753dd05
npm ERR! Actual:   91b4614652220585b11810f20d3887372acfbb0e
npm ERR! From:     https://registry.npmjs.org/generator-ionicjs/-/generator-ionicjs-0.2.5.tgz
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR!     at ReadStream.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR!     at ReadStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:920:16
npm ERR!     at process._tickCallback (node.js:415:13)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>
npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "generator-ionicjs"
npm ERR! cwd /Users/martin/development/presentation
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.6
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/martin/development/presentation/npm-debug.log
npm ERR! not ok code 0

[diegonetto]

Recently moved this package to generator-ionic and that is also experiencing this issue.

node 0.10.26
npm 1.3.24

[diegonetto]

Installed the latest npm 1.4.7 and was still having this issue when running npm install -g generator-ionic

The only thing that I was able to do was bump the version and republish the package. I feel like this is entirely out of our control so I'm not sure how to keep it from happening again.

[krasimir]

I found out that requesting a specific version works. Like for example:

npm install -g https://registry.npmjs.org/generator-ionicjs/-/generator-ionicjs-0.2.5.tgz

However, this is not a good solution. It looks like the problem is in the version of npm that publishes the module. I tried various but didn't find the proper one.

[othiym23]

Close! The problem is actually with node, not with npm. Node versions 0.11.6 (or so) through 0.11.13 all have a bug in their shasum implementation that cause packages published using them to have an incorrect shasum and to fail to install. The correct thing to do is to get the owners of the affected modules to use Node 0.10.28 to bump and republish the modules (and also to fix node, but that's already happened, and the fix will be in node 0.11.14 / 0.12).

[krasimir]

Aha, that's good news. Any idea when 0.11.14 will be released.

[othiym23]

That's a question for the node core team. As they're trying to get 0.12 out the door soon, my guess is that a new 0.11 build will be out the door even sooner.

[krasimir]

Thanks for the answer. I installed manually 0.11.13 (http://nodejs.org/dist/v0.11.13/) because there was a fix that I needed. But indeed it will be really cool if 0.12 come soon.