Current behaviour: Everytime I run npm install this file, package-lock.json gets created and gets added to the git changes.
Should this be ignored by git?
package-lock.json is a new concept introduced in NPM 5.0.0, released very recently. If this is anything like Rails' Gemfile.lock, then it needs to be source-controlled, but we'd need some time to study it first.
Noticed this too after updating npm on my system. I like the latest version; npm install completes much more quickly now :)
Ahh, understood @wkurniawan07. So for now, I shouldn't be committing the changes to package-lock.json along with PRs, correct?
It seems apt to add package-lock.json to VCS. @whipermr5 any thoughts?
Just read through https://docs.npmjs.com/files/package-lock.json. Sounds good!
To the one working on this issue: this also calls for making Node.js v8 the minimum requirement. Strictly speaking it's NPM v5, but since it comes under Node.js v8, we might as well make that one the minimum requirement, and Node.js v8 will be entering LTS phase soon anyway.
Done quite a while back
Most helpful comment
Noticed this too after updating
npmon my system. I like the latest version;npm installcompletes much more quickly now :)