Sometimes, you run into weird-looking errors with npm or while serving your solutions with Gulp. Since version 5, npm cache has had a self-healing mechanism that guarantees data to be valid.

If you need to verify that the npm cache is intact, run the following command:

npm cache verify 

This prints out the verification statistics:

You should never need to clean the npm cache, other than to free up more disk space. You can force the cache to empty its contents with the following command:

npm cache clean --force 

Run verify once again to verify that the cache was cleaned: