Remove --strict-peer-deps from npm install in CI

Since it causes npm install to fail with ERESOLVE on npm@^7.20.3 or npm@>=8.0.0 <8.1.1 due to the combination of eslint@^7.0.0 and eslint-plugin-node@^11.0.0: npm/cli#3868 (comment) Rather than updating npm on the runner during each CI run, remove --strict-peer-deps until a version of Node.js ships with npm@^8.1.1. Signed-off-by: Kevin Locke <[email protected]>
kevinoid · Nov 19, 2021 · ae9e87b · ae9e87b
1 parent 8608a49
commit ae9e87b
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/.github/workflows/node.js.yml b/.github/workflows/node.js.yml
@@ -39,7 +39,9 @@ jobs:
     - name: Display Node.js version
       run: node --version
     - name: Install dependencies
-      run: npm install --strict-peer-deps
+      # Note: Not using --strict-peer-deps until [email protected] ships with Node.js
+      # due to https://github.com/npm/cli/issues/3868
+      run: npm install
     - name: Lint
       run: npm run lint
     - name: Run tests
@@ -97,7 +99,9 @@ jobs:
     - name: Display Node.js version
       run: node --version
     - name: Install dependencies
-      run: npm install --strict-peer-deps
+      # Note: Not using --strict-peer-deps until [email protected] ships with Node.js
+      # due to https://github.com/npm/cli/issues/3868
+      run: npm install
     - name: Run tests
       run: npm run test-unit-cov
     # Note: Not uploading to Codecov, due to poor support for matrix builds