Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Regenerate integrity checks to sha512 #7399
I'm wondering if it all boils down to removing
At least this is how I was able to resolve the issue with seeing
AFAIK it is a caching issue, if npm had previously downloaded the same package/module version and stored it using a SHA1 hash then that is what is used when updating the lock file.
The typical fix is to
FWIW I enquired about this issue with npm support ~6 months ago as I believed there was anecdotal evidence that downloading from non-USA npm mirrors would cause an increase in instances of this issue, the resolution was to use the fix above and try again /shrug