update CI pipelines and contributing doc

Author: bowheart

.github/pull_request_template.md

@@ -4,7 +4,7 @@ Hello! Thanks for contributing to Zedux. Read this message and delete it to ackn
 
 Make sure you've followed the [contribution guidelines](https://github.com/Omnistac/zedux/blob/master/CONTRIBUTING.md). Specifically:
 
-- Make sure the first commit is formatted correctly (via running `yarn commit` in the repo root) and indicates all affected packages.
+- Make sure the first commit is formatted correctly (via running `pnpm commit` in the repo root) and indicates all affected packages.
 
   We'll use this to generate the changelog and release notes if your PR is merged. Any other commits will be squashed into the first commit. Each PR can only have one commit, so separate changes into separate PRs if needed.
 

.github/workflows/coverage.yml

@@ -15,9 +15,11 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: '20.x'
-      - run: yarn --frozen-lockfile
-      - run: yarn build
-      - run: yarn test
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+      - run: pnpm i --frozen-lockfile
+      - run: pnpm build
+      - run: pnpm test
       - name: Upload Coverage to Codecov
         uses: codecov/codecov-action@v5
         with:

.github/workflows/test.yml

@@ -21,6 +21,8 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: ${{ matrix.node-version }}
-      - run: yarn --frozen-lockfile
-      - run: yarn build
-      - run: yarn test
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+      - run: pnpm i --frozen-lockfile
+      - run: pnpm build
+      - run: pnpm test

.gitignore

@@ -7,5 +7,3 @@
 coverage
 dist
 node_modules
-yarn-debug.log*
-yarn-error.log*

CONTRIBUTING.md

@@ -2,20 +2,20 @@ Abide by the [code of conduct](CODE_OF_CONDUCT.md).
 
 ## Starting Development
 
-We use `yarn` to manage package dependencies. Simply running `yarn` in the repo root is all you need to get started with developing the packages.
+We use `pnpm` to manage package dependencies. Simply running `pnpm i` in the repo root is all you need to get started with developing the packages.
 
-We use Nx with yarn workspaces to manage the package-based monorepo. Every directory in the `packages/` folder is its own npm package. Run `yarn nx graph` to see the dependency graph of Zedux packages.
+We use Nx with pnpm workspaces to manage the package-based monorepo. Every directory in the `packages/` folder is its own npm package. Run `pnpm nx graph` to see the dependency graph of Zedux packages.
 
-We recommend Test-Driven Development for most Zedux code changes. Add integration tests and run `yarn test my-test-file` in the repo root to check changes.
+We recommend Test-Driven Development for most Zedux code changes. Add integration tests and run `pnpm run test my-test-file` in the repo root to check changes.
 
 ### Docs
 
-The docs are separated from the rest of the repo - they're not a yarn workspace. To run the docs site:
+The docs are separated from the rest of the repo - they're not a pnpm workspace. To run the docs site:
 
 ```sh
 cd docs
-yarn
-yarn start
+pnpm i
+pnpm start
 ```
 
 This sets up an HMR-enabled dev server for quickly previewing docs site changes.
@@ -28,7 +28,7 @@ Properly type everything - no `any`s unless it's the correct type or you demonst
 
 Add integration tests in the `test/integrations` folder of the appropriate package(s) to **fully** demonstrate all desired functionality. Unit tests aren't required if all functionality is covered well in integration tests, but they are a nice-to-have.
 
-Ensure that all tests pass by running `yarn test` in the repo root. That command will also output code coverage. Ensure that all changes have full Statement, Branch, Function, and Line coverage.
+Ensure that all tests pass by running `pnpm test` in the repo root. That command will also output code coverage. Ensure that all changes have full Statement, Branch, Function, and Line coverage.
 
 The PR title should be in the same format as the main commit. E.g. `feat(react): implement cool new thing`
 
@@ -40,15 +40,15 @@ Make the PR directly against Zedux `master` branch unless it's a hotfix for a sp
 
 If your PR can't be merged due to conflicts, rebase against Zedux master, resolve conflicts locally, and force push the changes.
 
-If your PR requires changes, you can push those as separate commits (only the first commit has to follow the [commit message guidelines](#commit-messages) via `yarn commit`. All other commits can be free-form via `git commit`). Or you can `git commit --amend` a previous commit and force push.
+If your PR requires changes, you can push those as separate commits (only the first commit has to follow the [commit message guidelines](#commit-messages) via `pnpm commit`. All other commits can be free-form via `git commit`). Or you can `git commit --amend` a previous commit and force push.
 
 ## Commit Messages
 
 We use a custom script to generate the CHANGELOG from commit messages. Thus commit messages must follow a specific format. This format is a simplification of the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) specification.
 
-Use `yarn commit` (in the repo root) instead of `git commit` to make our custom commit formatter tool automatically format these correctly for you.
+Use `pnpm commit` (in the repo root) instead of `git commit` to make our custom commit formatter tool automatically format these correctly for you.
 
-It's recommended to always use `yarn commit`, but if you want to know the format that it outputs, here it is:
+It's recommended to always use `pnpm commit`, but if you want to know the format that it outputs, here it is:
 
 ```
 <type>(<optional scope>): <description>

examples/socket-io/.gitignore

@@ -2,10 +2,7 @@
 logs
 *.log
 npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
 pnpm-debug.log*
-lerna-debug.log*
 
 node_modules
 dist