Closed cghislai closed 7 years ago
Sorry it works fine at home - probably due to the corporate proxy
I met this issue too,can you share the solution how you resolved ?
It was due to the corporate virus scanner. As the archive contained binaries, the proxy closed the connection during the scanning. Solution is to whitelist the url or to bring the binaries behind the firewall by other means.
Hi,
It looks like the npm 3.10.5 package in the dependencies is corrupted and the shasum check fails. I am behind a corporate proxy, but I doubt it is the cause: the downloaded tar archive cannot be processed by tar correctly neither.
Error: