From a8a148461af5da2ea209e8f67595096829f6e6cb Mon Sep 17 00:00:00 2001 From: djwx Date: Wed, 29 Sep 2021 16:20:04 -0400 Subject: [PATCH] Update index.md update to docs, as 'npm install' doesn't use 'exactly' the packages defined in package-lock.json, it will update package-lock.json based on semver of packages.json. 'npm ci' will do what the text describes' --- src/documentation/0020-package-lock-json/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/documentation/0020-package-lock-json/index.md b/src/documentation/0020-package-lock-json/index.md index e1d62f2984..92a294456a 100644 --- a/src/documentation/0020-package-lock-json/index.md +++ b/src/documentation/0020-package-lock-json/index.md @@ -26,7 +26,7 @@ It could be you, or another person trying to initialize the project on the other So your original project and the newly initialized project are actually different. Even if a patch or minor release should not introduce breaking changes, we all know bugs can (and so, they will) slide in. -The `package-lock.json` sets your currently installed version of each package **in stone**, and `npm` will use those exact versions when running `npm install`. +The `package-lock.json` sets your currently installed version of each package **in stone**, and `npm` will use those exact versions when running `npm ci`. This concept is not new, and other programming languages package managers (like Composer in PHP) use a similar system for years.