Skip to content
Permalink
Browse files
Prefer verbose npm command as bread crumb
Likely due to ignorance of the npm ecosystem, I found myself thinking
that `npm ci` was perhaps a directive to execute a **C**ontinuous
**I**ntegration workflow, rather than doing a clean install. Updating
these references in case any future developers share my ignorance.
  • Loading branch information
Landon Grindheim authored and GitHub committed May 5, 2022
1 parent 353b165 commit a3d7673b3034efe762c60f9b1930fe7ba6ed5011
Showing 4 changed files with 4 additions and 4 deletions.
@@ -26,7 +26,7 @@ jobs:
node-version: ${{ steps.nvm.outputs.NVMRC }}

- name: Install npm dependencies
run: npm ci
run: npm clean-install

- name: Rebuild the dist/ directory
run: npm run package
@@ -45,7 +45,7 @@ jobs:
node-version: ${{ steps.nvm.outputs.NVMRC }}

- name: Install npm dependencies
run: npm ci
run: npm clean-install

# If we're reacting to a Docker PR, we have on extra step to refresh and check in the container manifest,
# this **must** happen before rebuilding dist/ so it uses the new version of the manifest
@@ -27,7 +27,7 @@ jobs:
node-version: ${{ steps.nvm.outputs.NVMRC }}

- name: Install npm dependencies
run: npm ci
run: npm clean-install

- name: Pre-fetch the pinned images
run: npm run fetch-images
@@ -25,7 +25,7 @@ jobs:
node-version: ${{ steps.nvm.outputs.NVMRC }}

- name: Install npm dependencies
run: npm ci
run: npm clean-install

- name: Check formatting
run: npm run format-check

0 comments on commit a3d7673

Please sign in to comment.