running npm i gives error -> tarball data for @firstname.lastname@example.org (sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg=) seems to be corrupted. Trying one more time.
Likely due to a transient network problem. See: Shasum check or integrity/EINTEGRITY errors
Nope not a transient network error has been solid for the last three weeks.
Sometimes clearing the cache can help clear an earlier error. Run this to see what the alternatives are, or add
--force if you don’t mind clearing your cache.
npm cache clear
There have been networking problem reports here which turned out to be problems with particular parts of the internet, but I don’t know how to debug those.
As a small data point, I am not able to reproduce the issue:
% npm install @email@example.com npm WARN deprecated firstname.lastname@example.org: not actively maintained anymore npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN email@example.com No description npm WARN firstname.lastname@example.org No repository field. + @email@example.com added 9 packages from 8 contributors and audited 9 packages in 4.352s
Npm cache clear --force
Npm install @firstname.lastname@example.org reproduces the error verification failed while extracting @microsoft/ email@example.com integrity checksum failed when using sha1 but got sha512- etcetc etc
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.