4 ms·
You should always commit a lockfile (either npm's or yarn.lock) alongside package.json
by seattle_spring 5y ago
You should always commit a lockfile (either npm's or yarn.lock) alongside package.json
- TranquilMarmot 5y agoThis helps with CI and deploys, but on developer machines running `npm i` will install different things at different times. The amount of churn a `package-lock.json` file undergoes when all of the dependencies have a `^` is crazy.
- realityking 5y agoWhen you have a package-lock.json file npm i will not upgrade packages. You have to do that manually. The biggest churn in package-lock.json files is from using different npm versions. It’s worth keeping them aligned within a dev team.