CLI documentation update from CI

CI User · CI User · commit 53239cdfb992 · 2022-04-02T02:42:57.000Z
diff --git a/cli/v8 b/cli/v8
@@ -1 +1 @@
-Subproject commit 1a7d0d6f94c7f5e33e3426cf8e7a87dd7ad682dc
+Subproject commit 2829cb28a432b5ff7beeeb3bf3e7e2e174c1121d
diff --git a/content/cli/v8/commands/npm-ci.md b/content/cli/v8/commands/npm-ci.md
@@ -56,6 +56,13 @@ In short, the main differences between using `npm install` and `npm ci` are:
 * It will never write to `package.json` or any of the package-locks:
   installs are essentially frozen.
 
+NOTE: If you create your `package-lock.json` file by running `npm install`
+with flags that can affect the shape of your dependency tree, such as
+`--legacy-peer-deps`, you _must_ provide the same flags to `npm ci` or you
+are likely to encounter errors. An easy way to do this is to run
+`npm config set legacy-peer-deps=true --location=project` and commit the
+`.npmrc` file to your repo.
+
 ### Example
 
 Make sure you have a package-lock and an up-to-date install:
