https://github.com/posthog/posthog-rrweb
a complete copy of rrweb allowing us to vary CI
https://github.com/posthog/posthog-rrweb
Last synced: 5 months ago
JSON representation
a complete copy of rrweb allowing us to vary CI
- Host: GitHub
- URL: https://github.com/posthog/posthog-rrweb
- Owner: PostHog
- License: mit
- Created: 2025-01-20T14:02:50.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2026-01-13T02:12:36.000Z (6 months ago)
- Last Synced: 2026-01-13T05:49:07.940Z (6 months ago)
- Language: TypeScript
- Size: 9.88 MB
- Stars: 3
- Watchers: 5
- Forks: 0
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# PostHog's copy of RRWeb
this is open because we believe in open source,
and we want to be able to contribute back to upstream rrweb and refer back to this when we do
# but please don't use it yourself
all changes will be only focussed on posthog and we won't make any effort to support anybody else using this
if you say "i started using this, you changed it, and now my thing broke"
we will say "we told you not to use it"
The upstream rrweb is here https://github.com/rrweb-io/rrweb
## Hello internal PostHog folk
We build this and publish it to NPM so that we can use it in posthog-js
If you want to contribute a change back to upstream rrweb
then you need to open a person fork and contribute from there
### How to use it...
1. `pnpm install` to, erm, install
2. `pnpm build:all` to get a stable base built
3. `pnpm dev` to get auto building of changed things while making changes
4. `pnpm test` to run the tests
5. `pnpm test:update` to update snapshots if necessary
# FAQ
- does this mean you're planning on stopping using RRWEB?
- no
- can I use this repo?
- unless you are contributing changes for posthog, no
- should I sponsor rrweb?
- absolutely, yes. we do, you should too, it's great