chore: switch to pnpm

Author: bezoerb

.github/workflows/test.yml

@@ -26,19 +26,19 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: ${{ matrix.node }}
+          cache: pnpm
+          cache-dependency-path: pnpm-lock.yaml
 
-      - name: Cache Node Modules
-        id: cache-node-modules
-        uses: actions/cache@v4
+      - name: Set up pnpm
+        uses: pnpm/action-setup@v4
         with:
-          path: node_modules
-          key: node-modules-${{ hashFiles('package-lock.json') }}
+          version: 10.28.0
 
       - name: Install dependencies
-        run: npm ci
+        run: pnpm install
 
       - name: Run tests
-        run: npm run test:ci
+        run: pnpm run test:ci
 
       - name: SonarCloud Scan
         uses: SonarSource/sonarcloud-github-action@master

.husky/commit-msg

@@ -1 +1 @@
-npx --no -- commitlint --edit "$1"
+pnpm exec commitlint --edit "$1"

.husky/pre-commit

@@ -1 +1 @@
-npx --no-install lint-staged
+pnpm exec lint-staged

.npmrc

@@ -1 +1,2 @@
-lockfile-version=2
+prefer-workspace-packages=true
+shared-workspace-lockfile=true

CONTRIBUTING.md

@@ -51,14 +51,14 @@ Try and avoid making breaking changes. Those take more time to ship. Instead mak
 
 Features should be accompanied with tests and documentation.
 
-Don't include unrelated changes in your pull request. Make sure tests pass on your machine by running `npm test`. You can run specific test files as well using `npm run test -- packages/.../{file}.js`.
+Don't include unrelated changes in your pull request. Make sure tests pass on your machine by running `pnpm test`. You can run specific test files as well using `pnpm run test -- packages/.../{file}.js`.
 
 When you make a pull request please use a clear and descriptive title. Be specific about what's changed and why.
 
 Please make sure the *Allow edits from maintainers* box is checked. That way we can make certain minor changes ourselves, allowing your pull request to be merged sooner.
 
 You might be asked to make changes to your pull request. There's never a need to open another pull request. Push more commits to your existing branch. We'll squash them when we merge the PR.
 
-Dependencies are managed using `npm`. Only update dependencies when needed for your pull request. Don't rebuild the lockfile.
+Dependencies are managed using `pnpm`. Only update dependencies when needed for your pull request. Don't rebuild the lockfile.
 
 And finally, have fun!

jest.preset.js

@@ -14,7 +14,7 @@ export default {
       tsconfig: '<rootDir>/tsconfig.json',
     }]
   },
-  transformIgnorePatterns: ['node_modules/(?!(serialize-error)|(exit-hook)|(chalk)|(find-cache-dir)|(pkg-dir)|(find-up)|(locate-path)|(p-locate)|(p-limit)|(yocto-queue)|(path-exists)|(change-case))'],
+  transformIgnorePatterns: ['node_modules/(?!(\\.pnpm)|(serialize-error)|(exit-hook)|(chalk)|(find-cache-dir)|(pkg-dir)|(find-up)|(locate-path)|(p-locate)|(p-limit)|(yocto-queue)|(path-exists)|(change-case))'],
   preset: 'ts-jest/presets/js-with-ts-esm',
   moduleDirectories: ['node_modules', `${__dirname}/packages`],
   coverageReporters: ['text', 'clover', 'json', 'lcov'],

lerna.json

@@ -1,5 +1,6 @@
 {
   "version": "4.0.3",
+  "npmClient": "pnpm",
   "packages": ["packages/*"],
   "command": {
     "bootstrap": {