fix(iterate-com): bump posthog-js to 1.359.1 to fix cross-origin iframe recording error#1173
Merged
iterate[bot] merged 1 commit intomainfrom Mar 11, 2026
Conversation
…me recording error Upgrades posthog-js from 1.282.0 to 1.359.1 in the marketing site. This resolves a DOMException (SecurityError) in PostHog's session recording where rrweb's CrossOriginIframeMirror tries to access removeEventListener on a cross-origin iframe window. Fixed upstream in rrweb-io/rrweb#1695. Also fixes ThemeProvider types for compatibility with updated dependency graph.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
posthog-jsfrom1.282.0to1.359.1in the marketing site (apps/iterate-com)DOMException: SecurityErrorin PostHog's session recording where rrweb'sCrossOriginIframeMirrortries to accessremoveEventListeneron a cross-origin iframe window — fixed upstream in rrweb-io/rrweb#1695ThemeProvidertypes that broke due to updated dependency graph (next-themesPropsWithChildrenresolution)Context
Note
Medium Risk
Upgrades a third-party analytics/session-replay library (
posthog-js) with significant transitive dependency changes, which can affect runtime behavior and bundle size. Also tweaksThemeProviderprop typing/rendering, which could impact theming if props/children handling differs.Overview
Updates the marketing site to use
posthog-js@1.359.1(from1.282.0), pulling in updated transitive deps viapnpm-lock.yamlto address session-recording issues.Adjusts
ThemeProviderto acceptReact.PropsWithChildren<ThemeProviderProps>and forward props directly tonext-themes’ThemeProvider(<NextThemesProvider {...props} />) instead of explicitly wrappingchildren.Written by Cursor Bugbot for commit 09fc226. This will update automatically on new commits. Configure here.