I have a similar 'shasum' error on the completely different machines (Osx and Ubuntu) when running 'npm install' in the project root (generator mobile). Sometimes it trows an error on Grunt package, sometimes it trows an error on the Responsive images package (as below).
I've tried to reinstall Nodejs, Npm and Yeoman on both machines to make sure i'm running latest stable versions. Also tried to use some older versions of Nodejs and Npm to make sure it isn't a version conflict. I also did 'npm cache clean' several times, in fact yesterday i tried it on a fresh new installation of Ubuntu with the same negative result.
From what i heard the Npm registry is kinda 'buggy' atm, but i'm not sure if this problem is my fault. Would be great to get some insights or directions where to look for solutions.
Here is the error:
npm http 200 https://registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz
npm Error: shasum check failed
npm ERR! Expected: 313e82e3ef9dc07d15409eea1b12b25448d2cce0
npm ERR! Actual: e74135ce47e851b3be11716fad1e068b06593be7
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)
I have a similar 'shasum' error on the completely different machines (Osx and Ubuntu) when running 'npm install' in the project root (generator mobile). Sometimes it trows an error on Grunt package, sometimes it trows an error on the Responsive images package (as below).
I've tried to reinstall Nodejs, Npm and Yeoman on both machines to make sure i'm running latest stable versions. Also tried to use some older versions of Nodejs and Npm to make sure it isn't a version conflict. I also did 'npm cache clean' several times, in fact yesterday i tried it on a fresh new installation of Ubuntu with the same negative result.
From what i heard the Npm registry is kinda 'buggy' atm, but i'm not sure if this problem is my fault. Would be great to get some insights or directions where to look for solutions.
Here is the error: