more replacing

README.md

@@ -8,8 +8,8 @@ This README is intended for developing the library itself.
 
 ## Testing
 
-Unit tests: run `yarn test`.
-Cypress: run `yarn start` to have a test server running and separately `yarn cypress` to launch Cypress test engine.
+Unit tests: run `pnpm test`.
+Cypress: run `pnpm start` to have a test server running and separately `pnpm cypress` to launch Cypress test engine.
 
 ### Running TestCafe E2E tests with BrowserStack
 
@@ -28,7 +28,7 @@ in your shell env variables.
 
 After all this, you'll be able to run through the below steps:
 
-1. Optional: rebuild array.js on changes: `nodemon -w src/ --exec bash -c "yarn build-rollup"`.
+1. Optional: rebuild array.js on changes: `nodemon -w src/ --exec bash -c "pnpm build-rollup"`.
 1. Export browserstack credentials: `export BROWSERSTACK_USERNAME=xxx BROWSERSTACK_ACCESS_KEY=xxx`.
 1. Run tests: `npx testcafe "browserstack:ie" testcafe/e2e.spec.js`.
 
@@ -39,7 +39,7 @@ You can use the create react app setup in `playground/nextjs` to test posthog-js
 1. Run `posthog` locally on port 8000 (`DEBUG=1 TEST=1 ./bin/start`).
 2. Run `python manage.py setup_dev --no-data` on posthog repo, which sets up a demo account.
 3. Copy posthog token found in `http://localhost:8000/project/settings` and then
-4. `cd playground/nextjs`and run `NEXT_PUBLIC_POSTHOG_KEY='<your-local-api-key>' yarn dev`
+4. `cd playground/nextjs`and run `NEXT_PUBLIC_POSTHOG_KEY='<your-local-api-key>' pnpm dev`
 
 ### Tiers of testing
 

playground/nextjs/README.md

@@ -3,7 +3,7 @@
 First, run the development server:
 
 ```bash
-NEXT_PUBLIC_POSTHOG_KEY='<your-local-api-key>' yarn dev
+NEXT_PUBLIC_POSTHOG_KEY='<your-local-api-key>' pnpm dev
 ```
 
 Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.