Files
zeekay d63657d04e chore: kill posthog in docs + scripts; extend guard to .md/.sh
Sweeps the last holdouts my code-extension pass missed: 28 doc/script files
(READMEs, USAGE, CONTRIBUTING, insights-xcode.sh) and their host URLs ->
insights.hanzo.ai. Guard now covers .md and .sh too.

CHANGELOG.md is deliberately EXCLUDED from both the sweep and the guard:
published release notes are immutable history — rewriting them would be
dishonest about what shipped when.

Verified: zero posthog across code+docs+scripts, zero posthog-named files.
2026-07-16 09:13:13 -07:00

1.3 KiB

Insights'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 insights 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 Insights folk

We build this and publish it to NPM so that we can use it in insights-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

Releasing

Add a bump patch, bump minor, or bump major label to your PR before merging. The version bump and npm publish are automated on merge.

FAQ

  • does this mean you're planning on stopping using RRWEB?
    • no
  • can I use this repo?
    • unless you are contributing changes for insights, no
  • should I sponsor rrweb?
    • absolutely, yes. we do, you should too, it's great