title: How to prevent developers from modify node modules?
body: <p>We have our node_modules folder, like most do, I assume, located on the developer's PC, which the project grabs and uses when it needs to. I am having an issue where developers are opening these files, changing them, realized what they have done after their builder fails, but cannot recall what file they edited, and our source control does not watch NPM files. The only solution I have is to rm the entire node_modules and have our package-lock rebuild them at build time. Slow. I cannot simply make the files "read-only" or anything of the sort, as I don't have access to developer's PCs at any time.</p>
  
  <p>Any suggestions? Thank you.</p>
  
  <p>EDIT: So higher ups are wanting me to put the node_modules in our repo so that way mercurial watches them and will alert devs to when they changed one, which one they changed, and allow them to revert... I don't like the idea but so far this is the only idea available since, and I repeat, we cannot control what the devs do. This wouldn't be an issue if we could simply tell them "Don't do that".</p>