Repository navigation
Conversation
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.
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.