Just debugged a confusing problem with a user, where the
package-lock.json file wasn’t being updated when installing a new version of a dep. Turns out they had a
.npmrc file with
It’d be nice if npm warned when doing an install, if the package-lock.json file is present, and would be updated, but isn’t because of a config.
Maybe something like this:
npm WARN package-lock.json file present, but `package-lock=false` in config file: npm WARN /path/to/some/project/.npmrc npm WARN Update config or delete package-lock.json to silence this warning.