Regenerate integrity checks to sha512

[danielbachhuber]

From #7339 (comment)

[gziolo]

I'm wondering if it all boils down to removing node_modules folder locally and running npm install again. @ntwb, do you happen to know why those sha values change so often between local setups?

At least this is how I was able to resolve the issue with seeing package-lock.json modified after checking out the latest master.

[danielbachhuber]

I'm wondering if it all boils down to removing node_modules folder locally and running npm install again.

I was able to regenerate the sha512 values simply with npm install.

[ntwb]

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 npm cache clean --force when you find any patches you create are using SHA1/SHA256 in package-lock.json.

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

[gziolo]

Thanks @ntwb, let's get it in and try to avoid sha changes in package-json.lock in the future PRs. It should mitigate the issue. I'm sure we had the same issues with npm 5.6 or something.