We have a dedicated build cluster for our internal projects. These machines are managed by our DevOps team, and for them using NPM is a bit of a new experience.
But basically they require that the machine be in a pristine state before starting a build. And we have run into a couple of issue that looked fixed after running “npm cache clean --force”. I understand that this might have been simply fixed by re-running the build, but I also see their point, and so we’re probably going to add the cache clean command to every build script that uses NPM.
So the next issue is our DevOps really doesn’t like the “I sure hope you know what you are doing” warning message. Is there any way we can make that message a little more helpful? Like what actually is the downside of cleaning the cache… I assume it’s nothing more than causing the next “npm install” command to download everything and thus be slower. If that’s the case, can we change the message to just say that, like “The next call to
npm install will be slower due to needing to download all packages from the Internet” or some such…?
Thanks for your consideration.