It looks like every time we update our package-lock file for a Node.js project with NPM5 installed the build fails unless we rebuild without cache. It would be nice to detect if there are changes in the lock file and then invalidate the cache if that happens. Are other people experiencing this issue too?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Running npm install is adding a "name" key to the package-lock | 0 | 1649 | October 7, 2021 | |
| How to always rebuild without NPM cache | 7 | 11548 | June 18, 2018 | |
| Destroy npm cache (./node_modules/) based on a hash of package.json (or, if present: npm-shrinkwrap.json)? | 9 | 7737 | June 18, 2018 | |
| Clearing NPM Cache after upgrade | 3 | 7756 | June 18, 2018 | |
| Frequently getting npm 1.1.70 instead of correct installed version | 8 | 4937 | June 18, 2018 |