CLI documentation update from CI
CI User committed
Apr 2, 2022 at 02:42 UTC
53239cdfb992cd78436afd93065f51a06931ff0a
2 files changed
+8
-1
cli/v8
+1
-1
@@ -1 +1 @@
1
-Subproject commit 1a7d0d6f94c7f5e33e3426cf8e7a87dd7ad682dc
1
+Subproject commit 2829cb28a432b5ff7beeeb3bf3e7e2e174c1121d
content/cli/v8/commands/npm-ci.md
+7
@@ -56,6 +56,13 @@ In short, the main differences between using `npm install` and `npm ci` are:
56
* It will never write to `package.json` or any of the package-locks:
57
installs are essentially frozen.
58
59
+NOTE: If you create your `package-lock.json` file by running `npm install`
60
+with flags that can affect the shape of your dependency tree, such as
61
+`--legacy-peer-deps`, you _must_ provide the same flags to `npm ci` or you
62
+are likely to encounter errors. An easy way to do this is to run
63
+`npm config set legacy-peer-deps=true --location=project` and commit the
64
+`.npmrc` file to your repo.
65
+
66
### Example
67
68
Make sure you have a package-lock and an up-to-date install: