Remove package-lock.json? #3792
Closed
Labels
Comments
hmm, it shouldn't regenerate the lockfile. Otherwise, what's the point of a lockfile? Has this been reported to npm? |
It seems to be npm/npm#18135, open since August 10. No feedback from the npm team so far. |
Interesting that |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
npm 5, even the version included in the latest Node.js 8.5.0 re-generates
package-lock.json
on each install. And when it does on a system that doesn't support all the optional dependencies that are supported on the OS where the lockfile was generated, it removes those optional deps from the lockfile.The effect is that everyone firing
npm install
on our repo on any OS other than macOS will immediately get a dirty state of the repo as thefsevents
dependency subtree gets removed frompackage-lock.json
. That's a really bad experience.Link to test case
The text was updated successfully, but these errors were encountered: