Skip to content

Deliver startup telemetry after fatal frontend bootstrap errors - #123

Open
mzupan wants to merge 1 commit into
mainfrom
codex/frontend-bootstrap-telemetry-delivery
Open

mzupan wants to merge 1 commit into
mainfrom
codex/frontend-bootstrap-telemetry-delivery

Conversation

@mzupan

@mzupan mzupan commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

A fatal plugin or mount error currently stops the main module before RUM starts, leaving its buffered startup exception undelivered. Starting the dynamic import earlier is insufficient in production because Vite's SDK chunk imports a shared helper from the main entry module, and a failed entry module invalidates that dependency.

Schedule guarded plugin installation and mounting in a microtask after starting SDK loading. The entry module can finish evaluation, the original bootstrap exception is still rethrown as an uncaught browser error, and SDK initialization can subsequently deliver its bounded bootstrap event. Pre-mount Vue/router handlers, lazy SDK loading, opt-in configuration and the shared aggregate helper remain intact. Follow-up to merged #119.

Validation: 648 tests across 108 files plus production build/typecheck. Two entrypoint regressions throw during plugin installation or mounting before SDK loading completes. A production Chrome test injects a real DOM mount failure, observes the original uncaught error, then verifies SDK initialization and a delivered frontend_exception with source=bootstrap, stage=mount, count=1 and no exception text. The normal production smoke still passes all eleven operational event types, cookie/Origin transport, stream completion and outage recovery. Existing authenticated collector prerequisite is query-api #100.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant