Checksum fail when downloading as another user

This is a Bug Report

Description

I’ve published a package on Yith under my username, elsewhere my colleague has logged in and tries to download the package.

For bug reports:

• What went wrong? It failed with a checksum error.

• What did you expect should have happened? It should have downloaded the dependency as usual.

• What stacktrace or error message did you experience?

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node@6/6.9.5/bin/node" "/usr/local/bin/npm" "i" "-S" "yith-test"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10

npm ERR! shasum check failed for /var/folders/hy/5mcsh4rj4nqdr2dd7lsfzybr0000gn/T/npm-44837-8db82cdb/wgn99rpqrc.execute-api.eu-west-1.amazonaws.com/prod/registry/yith-test/-/yith-test-1.0.1.tgz
npm ERR! Expected: e4ef8ff55c945d69986138d3d390c41d1841cf9a
npm ERR! Actual:   298b1fe737fc503f48bc89e36ad063615bf9fc04
npm ERR! From:     https://wgn99rpqrc.execute-api.eu-west-1.amazonaws.com/prod/registry/yith-test/-/yith-test-1.0.1.tgz
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/hassankhan/Projects/yith-project-test/npm-debug.log

Additional Data

• NPM CLI version you are using: 3.10.10
• Serverless version you’re using: 1.6.1
• Node version you’re using: 6.9.5

[jonsharratt]

Is quite a hard one to debug, you can grab me on https://craftship-slack.herokuapp.com to join our Slack channel. Alternatively might be useful to screen hero, then lastly if you are based in London and prefer I could even pop over one Friday to try and crack what the issue is with this one.

One quick thing to try is a npm cache clean before trying the npm install again.

A more involved step if you have Charles is that you could try and log to see the requests and response data for the npm install but it requires a few steps:

• Trust the Charles SSL certificate (In Charles Help > SSL proxying > Install Charles Root Certificate)
• Trust your domain in SSL Proxy options of Charles (In Charles Proxy > SSL proxying settings... > Enable SSL Proxying > Add (your hostname and port 443 for the registry deployed))
• Disable strict SSL npm config set strict-ssl false
• npm set proxy http://localhost:8888
• Record in Charles and try to npm install the package

If you can post as much detail as possible for the requests and responses against the registry, then remember to:

• Re-enable strict SSL npm config set strict-ssl true
• Unset proxy npm config delete proxy

We will crack this 👍

[hassankhan]

I’m sorry, been swamped with work, will give it a go for sure tomorrow and will post back!