Skip to content

Update dependency posthog-js to v1.425.1 - #334

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-js-1.x-lockfile
Open

Update dependency posthog-js to v1.425.1#334
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-js-1.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Aug 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
posthog-js (source) 1.363.6 → 1.425.1 age confidence

Release Notes

PostHog/posthog-js (posthog-js)

v1.425.1

Compare Source

1.425.1

Patch Changes

  • #​4731 9b4008a Thanks @​fasyy612! - fix(replay): re-adopt constructed stylesheets when a shadow host is removed and re-added mid-replay. An SPA navigation can detach and reattach the same web component element; the browser keeps its shadow root and adopted sheets, so the recorder (which already tracks that shadow root) emits no new AdoptedStyleSheet event. The replayer rebuilds the element with a fresh shadow root and previously dropped the adopted styles for the rest of playback, rendering the component unstyled. The replayer now remembers the last adopted styleIds per host and re-adopts them when the shadow root is rebuilt, in both live playback and fast-forward. Fixes playback of existing recordings.
    (2026-09-02)

  • #​4744 77797c9 Thanks @​fasyy612! - fix(replay): keep recording through a session-id rotation when the persisted remote config is past its TTL. A rotation restart transits through stop() before start(), which made the config TTL check treat it as a cold boot: the stale config was discarded, start() bailed silently, and the recorder died with session attribution stuck on the old session id. The rotated session then shipped events with no initial full snapshot, producing recordings whose prefix cannot be played until something else restarted recording. Affects any rotation on a session older than one hour, most visibly posthog.reset() on logout. Cold-boot TTL behavior is unchanged.
    (2026-09-02)

v1.425.0

Compare Source

1.425.0
Minor Changes
Patch Changes

v1.424.1

Compare Source

1.424.1

Patch Changes
  • #​4711 d90b3c5 Thanks @​posthog! - Prevent failed replay network body reads from escaping into the host page's own fetch() call
    (2026-09-01)

v1.424.0

Compare Source

1.424.0

Minor Changes
  • #​4710 e87820a Thanks @​turnipdabeets! - Add os.name and os.version resource attributes to logs from the browser SDK, overridable via logs.resourceAttributes
    (2026-09-01)
Patch Changes

v1.423.2

Compare Source

v1.423.1

Compare Source

1.423.1

Patch Changes
  • #​4560 5931638 Thanks @​skvark! - Prevent stale session recorders from initializing after consent or session teardown, and dispose of recorders when switching to cookieless mode.
    (2026-09-01)

v1.423.0

Compare Source

1.423.0

Minor Changes

  • #​4663 6ae173f Thanks @​pauldambra! - Detect the Claude, Codex, and ChatGPT apps from their user agent markers: $browser now reports the app name instead of Chrome.

    ChatGPT versions its apps differently per platform, so its $browser_version is not comparable across platforms. (2026-09-01)

  • #​4659 1406e04 Thanks @​marandaneto! - Synchronize feature flag and early access enrollment persistence across browser tabs. Keep successful partial evaluations authoritative for payload updates and removals, including falsy payload values, while retaining cached state for failed evaluations.
    (2026-09-01)

Patch Changes

  • #​4696 aa72a36 Thanks @​github-actions! - Prefer data-ph-capture-attribute-* values from the closest element when the same property is defined on multiple ancestors.
    (2026-09-01)

  • #​4683 6309cb2 Thanks @​posthog! - Harden the directly importable getElementsChainString utility against runtime JavaScript callers that pass a non-array value. It now returns an empty string instead of calling .map on malformed input.
    (2026-09-01)

  • #​4708 6723395 Thanks @​turnipdabeets! - Change bigint attributes on logs, metrics and spans to send as an int64 rather than as a string.
    (2026-09-01)

  • #​4692 ec550b8 Thanks @​mhornbacher! - Respect navigator.globalPrivacyControl when respect_dnt is enabled
    (2026-09-01)

  • #​4697 6d6091e Thanks @​yfwmaniish! - Fix a memory leak in Session Replay recording: MutationBuffer skipped its own cleanup whenever a mutation batch normalized to an empty payload (e.g. a node added and removed within the same task), leaving the buffer holding strong references to DOM nodes indefinitely.
    (2026-09-01)

  • #​4672 0cddefe Thanks @​posthog! - Error tracking now drops a known uBlock Origin Lite exception thrown by its Safari extension. Safari masks extension content-script URLs as webkit-masked-url://hidden/, but also uses that URL for application code, so the filter requires the extension's error signature before dropping an all-masked stack. A remaining unmasked in_app frame still preserves the exception as first-party.
    (2026-09-01)

  • #​4704 cee2280 Thanks @​veryayskiy! - back off support widget polling to stop starving sends
    (2026-09-01)

  • #​4684 5874d1c Thanks @​yfwmaniish! - Fall back to in-memory storage when neither web storage nor cookies are available, instead of selecting a backend that cannot store anything. In contexts like a data: URL — a Figma plugin, for example — Chrome disables localStorage and cookies alike, and both the persistence and consent paths previously committed to an unusable store, logging a SecurityError on every capture. cookieStore._is_supported() now round-trips a probe cookie rather than only checking that document exists, and memoryStore no longer reports a stored falsy value (such as the 0 consent writes for "opted out") as absent.
    (2026-09-01)

  • #​4662 e7f5733 Thanks @​posthog! - Warn at init when persistence is 'memory' or 'sessionStorage' and no bootstrap.distinctID is set. In this setup the SDK mints a fresh distinct ID on every page load, so each identify() call merges another ID onto the same person. A person can then pass the distinct-ID limit, after which person pages and the session tab load only a truncated slice and the rest of the events look missing even though ingestion is fine. The warning points at the two fixes: switch to localStorage+cookie, or keep this persistence and pass a stable ID through bootstrap.distinctID.
    (2026-09-01)

  • #​4682 5c6ab6f Thanks @​posthog! - Fix an uncaught TypeError in the web vitals attribution bundle. The attributed INP observer read startTime from the first entry without a guard, so a report with no entries (for example after a bfcache restore or soft navigation) threw and stopped the metric capture. Bump web-vitals to 6.2.1, which guards the empty-entry case: instead of throwing, it reports the metric with fallback attribution that carries no interaction details (zeroed input and processing delays).
    (2026-09-01)

  • Updated dependencies [444bf35, 6ae173f, 6309cb2, 6723395]:

v1.422.5

Compare Source

1.422.5

Patch Changes

v1.422.4

Compare Source

1.422.4

Patch Changes
  • #​4626 3c650a1 Thanks @​nandinitiw! - Re-translate popover surveys when the display language changes while the survey is on screen, either from a browser languagechange event or from identify() updating the language person property. In-progress answers are preserved. $survey_questions[].question and $survey_language on survey sent / survey dismissed now report the text and language the user saw when they answered, not the language active when the event fired. Feedback-button (widget) surveys are unchanged.
    (2026-08-28)
  • Updated dependencies [3c650a1]:

v1.422.3

Compare Source

1.422.3

Patch Changes
  • #​4669 d0279e5 Thanks @​posthog! - Autocapture no longer throws a RangeError into the host page when it sorts element attributes. It now sorts attribute keys with a plain lexical comparator instead of localeCompare, which can throw on browsers with faulty ICU data.
    (2026-08-28)
  • Updated dependencies [d0279e5]:

v1.422.2

Compare Source

1.422.2

Patch Changes
  • #​4665 d5ef459 Thanks @​fasyy612! - Session replay can now bound DOM mutation bytes with an opt-in budget. Set __mutationBytesBucketSize (e.g. 1MB) to enable: mutations beyond the sustained budget (__mutationBytesRefillRate, default 25KB/s) are dropped and the recording resyncs with a full snapshot, keeping recordings from apps with very high DOM churn playable. Off by default.
    (2026-08-28)
  • Updated dependencies [d5ef459]:

v1.422.1

Compare Source

v1.422.0

Compare Source

1.422.0

Minor Changes
  • #​4658 db8687c Thanks @​posthog! - Report $sdk_debug_replay_throttled_mutations_dropped on captured events, counting the attribute changes the session recorder discarded during that session. The recorder throttles elements that change hundreds of times a second, and a discarded class or style change never reaches the player — so a recording can keep showing an element the live page had already hidden. Query this property to see whether your app is affected.
    (2026-08-27)

v1.421.2

Compare Source

1.421.2

Patch Changes

  • #​4653 712223a Thanks @​posthog! - Fix request timeouts never firing on pages where a browser extension makes Error.prototype.name non-writable
    (2026-08-27)

  • #​4036 718beee Thanks @​emmayusufu! - Fix logs.captureConsoleLogs set in init() not enabling console autocapture, capture console calls made before the logs script loads, and drop captured console records when the user opts out
    (2026-08-27)

  • #​4036 718beee Thanks @​emmayusufu! - Fix session replay and posthog-js leaving each other's console wrapper in the call path when either one stops
    (2026-08-27)

  • Updated dependencies [718beee, 712223a]:

v1.421.1

Compare Source

1.421.1

Patch Changes

  • #​4657 9c09bd4 Thanks @​marandaneto! - Use the best available compression for browser feature flag requests, preferring gzip when supported.
    (2026-08-27)

  • #​4520 362d081 Thanks @​veksa! - Drop sourcesContent from the source maps published to npm. The maps themselves still ship, so downstream source-map chaining and the //# sourceMappingURL references are unaffected — only the copy of our TypeScript sources embedded in each map is gone, taking the package from 40.8 MB to 17.4 MB unpacked. CDN artifacts are built separately and keep their inlined sources.
    (2026-08-27)

  • Updated dependencies [7902e44, e899b1c]:

v1.421.0

Compare Source

1.421.0

Minor Changes
  • #​4655 4f80973 Thanks @​robbie-c! - Add the 2026-08-30 config defaults. These defaults enable sanitized JSON-LD replay events.
    (2026-08-26)
Patch Changes

v1.420.0

Compare Source

1.420.0

Minor Changes
  • #​4640 0d2cf49 Thanks @​robbie-c! - Add opt-in Schema.org JSON-LD capture to session replay through session_recording.captureJsonLd. When enabled, the recorder emits sanitized JSON-LD as custom replay events and excludes all script elements from replay snapshots.
    (2026-08-26)
Patch Changes

  • #​4635 ab1383a Thanks @​robbie-c! - Capture paste interactions with clipboard autocapture without collecting pasted text.
    (2026-08-26)

  • #​4594 1d88b4e Thanks @​posthog! - Fix session replay playback ending when a recording contains a shadow host the browser refuses. The player now skips that one subtree instead of aborting the rebuild.
    (2026-08-26)

  • Updated dependencies [ab1383a, 0d2cf49]:

v1.419.4

Compare Source

1.419.4

Patch Changes

  • #​4592 ca540f9 Thanks @​dustinbyrne! - Add typed stable-name lookup for installed browser extensions and use it when independently loaded survey code resolves feature flags.
    (2026-08-25)

  • #​4533 53fcb2d Thanks @​dustinbyrne! - Fix console log autocapture silently failing when an older posthog-js core loads a newer logs bundle.
    (2026-08-25)

  • #​4476 ed4dd97 Thanks @​posthog! - fix(browser): refresh configured feature flags when a hidden tab becomes visible

    Feature flags now own their automatic refresh timer and visibility listener.
    Hidden tabs reload due flags when they become visible. The existing five-minute
    default and remote_config_refresh_interval_ms behavior remain unchanged. (2026-08-25)

  • Updated dependencies [53fcb2d, ca540f9, ed4dd97]:

v1.419.3

Compare Source

v1.419.2

Compare Source

1.419.2

Patch Changes

  • #​4645 cb7cc12 Thanks @​turnipdabeets! - Type declarations no longer import the JSX namespace from react, so they typecheck against @types/react back to the declared 16.8.0 floor. Component return types are now spelled ReactElement<any, any>, which is the definition of JSX.Element — the same type, so consuming code is unaffected.

    JSX only became an exported member of the react types module in @types/react@18.2.6, so projects on older React types previously saw TS2305: Module '"react"' has no exported member 'JSX' when checking these declarations with skipLibCheck: false. (2026-08-25)

v1.419.1

Compare Source

1.419.1

Patch Changes

  • #​4638 d166e54 Thanks @​github-actions! - Declare react and @types/react as optional peer dependencies so the posthog-js/react entry point can resolve React on strict node_modules layouts — pnpm and bun isolated linkers backed by a global store, where the package is installed outside the project tree and Node's directory walk never reaches the app's React.

    Projects that do not import posthog-js/react are unaffected: the peers are optional, so npm, pnpm, yarn, and bun install them only when React is already present and emit no unmet-peer warnings. (2026-08-25)

v1.419.0

Compare Source

1.419.0

Minor Changes
  • #​4598 334159b Thanks @​posthog! - Web vitals now capture attribution by default for INP and LCP, so a slow interaction or paint arrives with the target element and phase breakdown that make it diagnosable. CLS stays without attribution by default, because its attribution holds detached DOM nodes and can leak memory in single-page apps. Set capture_performance.web_vitals_attribution to false to opt out, true for every metric, or an array to name the metrics. The captured metric also drops the empty entries array and bounds attribution to a small set of useful fields, and the attributed INP observer no longer collects the processedEventEntries we never read.
    (2026-08-25)
Patch Changes

v1.418.17

Compare Source

1.418.17

Patch Changes

v1.418.16

Compare Source

1.418.16

Patch Changes
  • #​4607 7ec4f0d Thanks @​posthog! - Drop exceptions thrown by user scripts the browser injects into every page (Firefox for iOS, Chrome for iOS) instead of reporting them as the page's own errors. Set error_tracking.captureExtensionExceptions: true to keep capturing them.
    (2026-08-24)
  • Updated dependencies [7ec4f0d]:

v1.418.15

Compare Source

1.418.15

Patch Changes

v1.418.14

Compare Source

1.418.14

Patch Changes

v1.418.13

Compare Source

1.418.13

Patch Changes

  • #​4418 be2161d Thanks @​posthog! - feat: add granular automatic pageview options for SPA navigation

    capture_pageview now accepts an object with path, search, and hash options. Each selected URL component triggers a $pageview when it changes, including direct hash changes used by hash-based routers. The existing 'history_change' option continues to capture pathname changes. (2026-08-24)

  • Updated dependencies [be2161d]:

v1.418.12

Compare Source

1.418.12

Patch Changes
  • #​4501 9e853c1 Thanks @​posthog! - Session replay: fixed a stale element left rendered in the player when a mutation re-added a node id with changed attributes. Affects both useVirtualDom modes.
    (2026-08-24)

v1.418.11

Compare Source

1.418.11

Patch Changes

  • #​4603 ca030a6 Thanks @​martinfrancois! - Stop adding PostHog's optional feature scripts, such as the session replay recorder and exception autocapture, to the page more than once. Sites that proxy PostHog through their own domain, by setting api_host to a path like /ingest rather than a full URL, ended up with the same <script> tag three or four times: the check meant to spot the duplicate compared the browser's resolved absolute URL against the relative one, so it never matched. The network tab showed a single request either way, because the browser served the repeats from its cache, which is why this was easy to miss. Nothing measurable got slower as a result, so this is a correctness fix rather than a speed one.
    (2026-08-24)

  • #​4453 325870a Thanks @​posthog! - When session replay is waiting on a trigger, debug mode now names the conditions that haven't matched yet (for example buffering: URL condition not matched, or the named trigger group whose condition is pending) instead of only reporting buffering. Enable it with posthog.debug(). Logged once per change, not once per flush.
    (2026-08-24)

v1.418.10

Compare Source

1.418.10

Patch Changes

  • #​4451 e1d993c Thanks @​posthog! - Guard the replayer's hover handling against non-element and detached hover targets, which previously threw an unhandled TypeError (querySelectorAll on a node without that method) and stopped session recording playback mid-stream.
    (2026-08-21)

  • #​4557 4451274 Thanks @​posthog! - Keep replay playback running when a recording adopts constructed stylesheets across a document swap. A constructed stylesheet can only be adopted by the document that created it, so a sheet held over a swap is rejected and the error previously stopped the player. Adoption now falls back to whatever is already applied.
    (2026-08-21)

v1.418.9

Compare Source

1.418.9

Patch Changes
  • #​4588 c8df61c Thanks @​clr182! - fix(replay): attribute the backdated sessionIdle marker to the session that went idle, so a rotation-born session's recording no longer starts hours before its first snapshot
    (2026-08-21)

v1.418.8

Compare Source

1.418.8

Patch Changes
  • #​4583 6322f09 Thanks @​turnipdabeets! - Fix logs and metrics being silently dropped when an attribute holds a very large integer, a function, a symbol, a sparse array, or a truncated emoji.
    Cap log and metric attributes at 20 levels of nesting, 1,000 entries per object and 10,000 values in total, marking anything beyond as [Truncated].
    Type OtlpAnyValue.intValue as string | number — code reading that field must handle both. (2026-08-21)
  • Updated dependencies [6322f09]:

v1.418.7

Compare Source

v1.418.6

Compare Source

1.418.6

Patch Changes

  • #​4578 bae46bf Thanks @​marandaneto! - Drop events when a before-send hook throws instead of sending the unmodified event.
    (2026-08-20)

  • #​4582 aef2f49 Thanks @​ablaszkiewicz! - Stop building a stack frame for a window.onerror report that carries no code position, such as the ResizeObserver loop warning. The frame named the document URL rather than a script, so no source map could resolve it. These exceptions now arrive with no stack trace.
    (2026-08-20)

  • Updated dependencies [bae46bf, aef2f49]:

v1.418.5

Compare Source

1.418.5

Patch Changes

v1.418.4

Compare Source

1.418.4

Patch Changes
  • #​4309 b564d61 Thanks @​posthog! - Fix session recording in the full browser bundles. array.full.js and module.full.es.js only inlined rrweb, so they still fetched the recorder script at runtime - the request the full bundles exist to avoid. They now inline the whole recorder. Also flags the session with $sdk_debug_recording_script_not_loaded when the recorder script fails to load, so a blocked recorder is visible in analytics rather than only in the console.
    (2026-08-19)

v1.418.3

Compare Source

1.418.3

Patch Changes
  • #​4558 3f9ba71 Thanks @​posthog! - Fall back to the synthetic exception stack when a captured Error has no stack, so frameless failures (such as a Firefox network fetch TypeError) keep their call-site frames and group per call site instead of merging into one issue.
    (2026-08-19)
  • Updated dependencies [3f9ba71]:

v1.418.2

Compare Source

1.418.2

Patch Changes

  • #​4555 3e0edff Thanks @​HaynesPostHog! - Fix a Chrome renderer crash (grey "Aw, Snap" tab, "Error code: 5") that could still occur when closing an in-app survey on a heavy page such as a large dashboard.

    Closing a survey animated the fade-out with document.startViewTransition, which snapshots the entire page viewport. The survey applied no view-transition-name scoping, so on a heavy host page capturing that whole-page snapshot could exhaust renderer memory and crash the tab. A previous fix addressed a related crash (a snapshot pointing at a removed node) but left the document-level transition — and its whole-page snapshot cost — in place.

    The survey renders in an isolated shadow root, so it never needed a document-level transition. The close now fades the popup out with a plain CSS opacity transition scoped to the survey's own container, then unmounts it once the fade has run. No whole-page snapshot, no crash, same fade-out UX. (2026-08-19)

v1.418.1

Compare Source

1.418.1

Patch Changes
  • #​4549 0599fe0 Thanks @​ablaszkiewicz! - Recognise Firefox and Safari extension frames when filtering extension exceptions, and stop counting Safari's masked webkit-masked-url:// frames as in-app code.
    (2026-08-18)
  • Updated dependencies [0599fe0]:

v1.418.0

Compare Source

1.418.0

Minor Changes
  • #​4496 1ade666 Thanks @​marandaneto! - Add cookieWinsOnConflict to keep shared cross-subdomain identity and session state ahead of stale per-origin localStorage, deprecate __preview_cookie_wins_on_conflict, and enable the new behavior for the 2026-08-29 defaults.
    (2026-08-18)
Patch Changes

v1.417.4

Compare Source

1.417.4

Patch Changes
  • #​4509 8d74821 Thanks @​ksvat! - Take a full snapshot when session recording wakes from idle if DOM mutations were dropped while idle, so replay no longer shows duplicated or overlapping DOM after an idle period.
    (2026-08-17)

v1.417.3

Compare Source

1.417.3

Patch Changes

v1.417.2

Compare Source

1.417.2

Patch Changes
  • #​4413 7b61aa4 Thanks @​posthog! - Fix error tracking coercion reporting the wrong exception type for non-Error objects (e.g. TypeError, ReferenceError) that are thrown by browser extensions or other cross-realm code. Previously these always reported as type Error, burying the real type in the message string. Also fixed a local isError helper shadowing the more robust cross-realm-aware implementation, which caused some errors thrown from iframes or extension isolated worlds to be misclassified.
    (2026-08-17)
  • Updated dependencies [7b61aa4]:

v1.417.1

Compare Source

1.417.1

Patch Changes

  • #​4521 0a0206f Thanks @​marandaneto! - Normalize capture timestamp overrides to equivalent UTC ISO strings in the browser and Node.js SDKs and shared core.
    (2026-08-14)

  • #​4523 6230b5b Thanks @​marandaneto! - Prevent swallowed rrweb observer initialization errors from breaking session replay teardown and subsequent recorder restarts.
    (2026-08-14)

  • #​4503 eb05237 Thanks @​pauldambra! - fix(dead-clicks): treat visibility and focus changes as liveness signals, not dead-click evidence

    The dead-click detector treated a visibilitychange as evidence a click was dead: it measured Math.abs(clickTimestamp - lastVisibilityChange) and, once that exceeded the threshold, timed the click out as dead. Because it only recorded the tab becoming visible, any click in a session where the tab had ever been backgrounded (median gap ~1 minute) was flagged.

    A visibility or focus change near a click is the opposite — a sign the click did something (it woke/focused the tab, opened a new tab, or opened a new window/popup) — so these signals now only ever suppress a dead click, never cause one:

    • Visibility changes are recorded in both directions (a click that opens a new tab sends the current tab to hidden), and a window focus/blur observer is added, since a click that opens a new window/popup may leave the tab visible and only surface as the current window losing focus.
    • A click within a wake-up/interaction window (1s, wide enough for a real "tab back, then click" gesture) of any such change is suppressed.
    • The visibility signal no longer feeds the dead-marking path at all. $dead_click_visibility_changed_timeout stays in the payload (always false) for shape compatibility, and a new $dead_click_focus_changed_delay_ms is emitted for observability.
    • Visibility/focus changes are now recorded onto each queued candidate the instant they fire (like scroll), instead of being read from a single shared timestamp when the click is checked ~1s later. A click that hides or blurs the tab (opening a new tab/window) suspends that check while the tab is backgrounded; by the time it resumes the tab has usually returned, and the shared timestamp would have been overwritten by that later transition — losing the click-correlated one and wrongly flagging the click dead. Stamping the candidate as the event fires makes delayed hide→show and blur→focus sequences suppress correctly. (2026-08-14)

  • Updated dependencies [0a0206f, eb05237]:

v1.417.0

Compare Source

1.417.0

Minor Changes
  • #​4485 8bc63c3 Thanks @​dustinbyrne! - Default external dependency loading to versioned asset paths with automatic fallback to legacy paths, and add a strict_script_versioning: 'fallback' mode.
    (2026-08-13)
Patch Changes

v1.416.1

Compare Source

1.416.1

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • Between 12:00 AM and 11:59 PM (* 0-23 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Aug 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-beautiful-dnd@13.1.1
npm error Found: react@19.2.4
npm error node_modules/react
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error       node_modules/@mui/lab
npm error         @mui/lab@"^7.0.1-beta.19" from the root project
npm error       4 more (@mui/material, @mui/styled-engine, @mui/system, the root project)
npm error     peerOptional @emotion/react@"^11.5.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     5 more (@mui/material, @mui/styled-engine, @mui/system, ...)
npm error   peer react@">=16.8.0" from @emotion/styled@11.14.1
npm error   node_modules/@emotion/styled
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/material@7.3.9
npm error     node_modules/@mui/material
npm error       peer @mui/material@"^7.3.9" from @mui/icons-material@7.3.9
npm error       node_modules/@mui/icons-material
npm error         @mui/icons-material@"^7.3.5" from the root project
npm error       2 more (@mui/lab, the root project)
npm error     3 more (@mui/styled-engine, @mui/system, the root project)
npm error   30 more (@emotion/use-insertion-effect-with-fallbacks, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error node_modules/react-beautiful-dnd
npm error   react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error   node_modules/react-beautiful-dnd
npm error     react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-03T14_33_48_813Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-03T14_33_48_813Z-debug-0.log

@vercel

vercel Bot commented Aug 20, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
adminv2 Ready Ready Preview Sep 2, 2026 9:53pm UTC

Request Review

@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from cdbe3a2 to e2b64fa Compare August 20, 2026 15:55
@renovate renovate Bot changed the title Update dependency posthog-js to v1.418.5 Update dependency posthog-js to v1.418.6 Aug 20, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from e2b64fa to 65b6061 Compare August 20, 2026 21:55
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 65b6061 to 38d57fe Compare August 21, 2026 15:32
@renovate renovate Bot changed the title Update dependency posthog-js to v1.418.6 Update dependency posthog-js to v1.418.10 Aug 21, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 38d57fe to 793275b Compare August 25, 2026 12:46
@renovate renovate Bot changed the title Update dependency posthog-js to v1.418.10 Update dependency posthog-js to v1.418.16 Aug 25, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 793275b to 1a3138b Compare August 25, 2026 22:03
@renovate renovate Bot changed the title Update dependency posthog-js to v1.418.16 Update dependency posthog-js to v1.419.4 Aug 25, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 1a3138b to 9a3076e Compare August 26, 2026 11:45
@renovate renovate Bot changed the title Update dependency posthog-js to v1.419.4 Update dependency posthog-js to v1.420.0 Aug 26, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 9a3076e to e2c60ea Compare August 26, 2026 22:21
@renovate renovate Bot changed the title Update dependency posthog-js to v1.420.0 Update dependency posthog-js to v1.421.0 Aug 26, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from e2c60ea to ffa44de Compare August 27, 2026 11:56
@renovate renovate Bot changed the title Update dependency posthog-js to v1.421.0 Update dependency posthog-js to v1.421.1 Aug 27, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from ffa44de to a9c1e04 Compare August 27, 2026 16:54
@renovate renovate Bot changed the title Update dependency posthog-js to v1.421.1 Update dependency posthog-js to v1.422.0 Aug 27, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from a9c1e04 to c45c75c Compare August 27, 2026 22:14
@renovate renovate Bot changed the title Update dependency posthog-js to v1.422.0 Update dependency posthog-js to v1.422.1 Aug 27, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from c45c75c to 6cc1f3c Compare August 28, 2026 12:51
@renovate renovate Bot changed the title Update dependency posthog-js to v1.422.1 Update dependency posthog-js to v1.422.2 Aug 28, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 6cc1f3c to e467100 Compare August 28, 2026 21:10
@renovate renovate Bot changed the title Update dependency posthog-js to v1.422.2 Update dependency posthog-js to v1.422.5 Aug 28, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from e467100 to 2b95db8 Compare September 1, 2026 18:13
@renovate renovate Bot changed the title Update dependency posthog-js to v1.422.5 Update dependency posthog-js to v1.424.0 Sep 1, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 2b95db8 to 49c673c Compare September 1, 2026 22:08
@renovate renovate Bot changed the title Update dependency posthog-js to v1.424.0 Update dependency posthog-js to v1.424.1 Sep 1, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 49c673c to 815e220 Compare September 2, 2026 11:59
@renovate renovate Bot changed the title Update dependency posthog-js to v1.424.1 Update dependency posthog-js to v1.425.0 Sep 2, 2026
@renovate
renovate Bot force-pushed the renovate/posthog-js-1.x-lockfile branch from 815e220 to 80824d7 Compare September 2, 2026 21:49
@renovate renovate Bot changed the title Update dependency posthog-js to v1.425.0 Update dependency posthog-js to v1.425.1 Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants