C:\Users\you name>npm cache clean
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\you name\AppData\Roaming\npm-cache\_logs\2019-05-12T07_07_25_826Z-debug.log
Solution Since npm 5 uses a new package management model, so after upgrading, please clear about the local cache:
npm cache clean --force 。
If the top is no way to solve the problem, you can try the following instructions:
npm cache clear --force && npm install --no-shrinkwrap --update-binary C:\Users\you name>npm cache clean
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\you name\AppData\Roaming\npm-cache\_logs\2019-05-12T07_07_25_826Z-debug.log
Solution Since npm 5 uses a new package management model, so after upgrading, please clear about the local cache:
npm cache clean --force 。
If the top is no way to solve the problem, you can try the following instructions:
npm cache clear --force && npm install --no-shrinkwrap --update-binary