orange-tailor-8542310/29/2018, 8:25 PM
to ensure others pick up the exact same versions. This is generally a good idea for any shared codebase.
orange-tailor-8542310/29/2018, 8:31 PM
creamy-potato-2940210/29/2018, 8:52 PM
it will try to find versions of the dependencies that satisfy the constraints specified in
to choose the same versions of these dependencies, even on different machiines, and even if a new version has been released,
is important to have because it does what it says and locks the packages to specific versions. Make sense?
quaint-queen-3789610/29/2018, 9:59 PM
to actually pull the same package-lock bits
If dependencies in the package lock do not match those in package.json, npm ci will exit with an error, instead of updating the package lock.
uses the "latest patch" syntax, it's highly likely that two installs can pull down different versions.
npm install --save