For information on using this library in your app, see PostHog Docs.
This README is intended for developing the library itself.
Unit tests: run pnpm test
.
Cypress: run pnpm start
to have a test server running and separately pnpm cypress
to launch Cypress test engine.
Testing on IE11 requires a bit more setup. TestCafe tests will use the
playground application to test the locally built array.full.js bundle. It will
also verify that the events emitted during the testing of playground are loaded
into the PostHog app. By default it uses https://app.posthog.com and the
project with ID 11213. See the testcafe tests to see how to override these if
needed. For PostHog internal users ask @benjackwhite or @hazzadous to invite you
to the Project. You'll need to set POSTHOG_API_KEY
to your personal API key, and
POSTHOG_PROJECT_KEY
to the key for the project you are using.
You'll also need to sign up to BrowserStack. Note that if you are using CodeSpaces, these variables will already be available in your shell env variables.
After all this, you'll be able to run through the below steps:
- Optional: rebuild array.js on changes:
nodemon -w src/ --exec bash -c "pnpm build-rollup"
. - Export browserstack credentials:
export BROWSERSTACK_USERNAME=xxx BROWSERSTACK_ACCESS_KEY=xxx
. - Run tests:
npx testcafe "browserstack:ie" testcafe/e2e.spec.js
.
You can use the create react app setup in playground/nextjs
to test posthog-js as an npm module in a Nextjs application.
- Run
posthog
locally on port 8000 (DEBUG=1 TEST=1 ./bin/start
). - Run
python manage.py setup_dev --no-data
on posthog repo, which sets up a demo account. - Copy posthog token found in
http://localhost:8000/project/settings
and then cd playground/nextjs
and runNEXT_PUBLIC_POSTHOG_KEY='<your-local-api-key>' pnpm dev
- Unit tests - this verifies the behavior of the library in bite-sized chunks. Keep this coverage close to 100%, test corner cases and internal behavior here
- Cypress tests - integrates with a real chrome browser and is capable of testing timing, browser requests, etc. Useful for testing high-level library behavior, ordering and verifying requests. We shouldn't aim for 100% coverage here as it's impossible to test all possible combinations.
- TestCafe E2E tests - integrates with a real posthog instance sends data to it. Hardest to write and maintain - keep these very high level
Install Yalc to link a local version of posthog-js
in another JS project: npm install -g yalc
- In the
posthog-js
directory:yalc publish
- In the other directory:
yalc add posthog-js
, then install dependencies
(forposthog
this means:yalc add posthog-js && pnpm i && pnpm copy-scripts
)
- In the other directory:
yalc update
, then install dependencies
(forposthog
this means:yalc update && pnpm i && pnpm copy-scripts
)
- In the other directory:
yalc remove posthog-js
, then install dependencies
(forposthog
this means:yalc remove posthog-js && pnpm i && pnpm copy-scripts
)
Just put a bump patch/minor/major
label on your PR! Once the PR is merged, a new version with the appropriate version bump will be released, and the dependency will be updated in posthog/PostHog โ automatically.
If you want to release a new version without a PR (e.g. because you forgot to use the label), check out the main
branch and run npm version [major | minor | patch] && git push --tags
- this will trigger the automated release process just like the label.
To release an alpha or beta version, you'll need to use the CLI locally:
- Make sure you're a collaborator on
posthog-js
in npm (check here). - Make sure you're logged into the npm CLI (
npm login
). - Check out your work-in-progress branch (do not release an alpha/beta from
main
). - Run the following commands, using the same bump level (major/minor/patch) as your PR:
npm version [premajor | preminor | prepatch] --preid=beta npm publish --tag beta git push --tags
- Enjoy the new prerelease version. You can now use it locally, in a dummy app, or in the main repo.