chore(replay): bump @posthog/rrweb to 0.0.59#55746
Conversation
|
Hey @pauldambra! 👋\nThis pull request seems to contain no description. Please add useful context, rationale, and/or any other information that will help make sense of this change now and in the distant Mars-based future. |
|
Reviews (1): Last reviewed commit: "chore(replay): bump @posthog/rrweb to 0...." | Re-trigger Greptile |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
Size Change: +42.7 kB (+0.03%) Total Size: 130 MB
ℹ️ View Unchanged
|
regenerate rr-web-schema.json to include displayWidth/displayHeight canvas mutation fields added in PostHog/posthog-rrweb#137 Generated-By: PostHog Code Task-Id: 5b092d28-8278-4b17-8154-200c54457eb3
pauldambra
force-pushed
the
04-22-chore_replay_bump_posthog_rrweb_to_0.0.59
branch
from
bbf30b7 to
3136ea6
Compare
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
2 participants
Problem
We are 33 versions behind on the PostHog fork of rrweb. Latest is
0.0.59(published 2026-04-22); we were pinned to0.0.26(2025-10-10).The gap includes a bunch of replay/player bug fixes we want in production (replay flicker, iframe/weakmap leaks, doctype + custom element hardening,
SecurityErrorhandling in iframe cleanup, nested CSS handling, adopted-stylesheet clears, etc.), plus recorder-side fixes (canvas dedup, OffscreenCanvas fallbacks, iframe observer leaks, postcss-removal from the bundle).Changes
frontend/package.json,common/replay-shared/package.json,common/replay-headless/package.json: bump@posthog/rrweb,@posthog/rrweb-types,@posthog/rrweb-plugin-console-recordfrom0.0.26→0.0.59pnpm-lock.yamlregenerated. Transitive@posthog/rrweb-snapshot,@posthog/rrweb-utils,@posthog/rrdomgo from0.0.4→0.0.59to match.PostHog/posthog-rrweb PRs rolled in
Replay player
Recorder
Chores / infra (non-code-affecting): #93, #96, #98, #103, #105, #106, #107, #109, #110, #111, #112, #114, #115, #117, #118, #119, #120, #144, #146, #149, #161, #165, #170
How did you test this code?
I am an agent, so this was tested in code only — no manual browser smoke test yet:
pnpm --filter=@posthog/frontend typescript:check— no new type errors in any rrweb-consuming file. (There are 77 pre-existing errors inproducts/workflows/frontend/*, all unrelated to this change.)hogli test frontend/src/scenes/session-recordings/player— 251/251 tests pass. Some suites failed to load due to a pre-existing@posthog/hogvmmodule-resolution issue in unrelated files (saved-insights,max,PathCleanFilters); none of those failures are caused by the rrweb bump.Reviewer smoke test recommended before merge: run
./bin/start, open a recent session replay, and play it end-to-end (scrub, pause, network tab, iframe-heavy recording, canvas recording if available). Confirm no console errors and no replay flicker.Publish to changelog?
no
🤖 LLM context
Authored by PostHog Code (Claude Opus 4.7). Task ID
5b092d28-8278-4b17-8154-200c54457eb3. The full list of posthog-rrweb PRs above was pulled fromgh pr list --repo PostHog/posthog-rrweb --state merged --search "merged:>=2025-10-10". TypeScript/types surfaces used by consumers (Replayer,ReplayPlugin,playerConfig,eventWithTime,EventType,IncrementalSource) did not need any consumer-side adaptation.Created with PostHog Code