chore: generate lockfile for audit, install speed

Author: wkillerud

.github/workflows/release.yml

@@ -24,19 +24,15 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
 
-      - name: Install Node.js
-        uses: actions/setup-node@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 20
 
-      - name: Install dependencies
-        run: npm install
+      - run: npm ci
 
-      - name: Run all tests
-        run: npm test
+      - run: npm test
 
-      - name: Release and publish
-        run: npx semantic-release
+      - run: npx semantic-release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/test.yml

@@ -20,11 +20,8 @@ jobs:
         with:
           node-version: ${{ matrix.node-version }}
 
-      - name: Install dependencies
-        run: npm install
+      - run: npm ci
 
-      - name: Lint
-        run: npm run lint
+      - run: npm run lint
 
-      - name: Run tests
-        run: npm test
+      - run: npm test

.gitignore

@@ -6,6 +6,5 @@ tmp/**/*
 .idea/**/*
 *.iml
 *.log
-package-lock.json
 .nyc_output
 .tap

.npmrc

@@ -1,2 +1,18 @@
-package-lock=false
+; Don't download optionalDependencies and peerDependencies.
+; Conflicting peerDependencies is a source of issues with npm install.
+; This setting forces us to be explicit about listing dependencies.
+omit=optional
+omit=peer
+
+registry=https://registry.npmjs.org
+
+; Prefer specifying dependency versions explicitly. Renovate will open
+; pull requests that handle most dependency updates for you.
 save-exact=true
+
+; Treat conflicting peerDependencies as a failure,
+; even if npm can reasonably guess an appropriate resolution.
+strict-peer-deps=true
+
+; Renovate will update packageManager for us.
+update-notifier=false