feat(remix): Add Remix 3 browser SDK with a bundled client entry - #24802
Draft
chargome wants to merge 1 commit into
Conversation
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Remix 3 has no bundler, so the browser gets whatever module graph the client entry reaches, and nothing can be eliminated. The entry is a named export list rather than a wildcard re-export, and it is bundled once at publish time into a single tree shaken file. Unbundled it costs an app 255 requests and about 364 KB gzipped; bundled it is 2 requests and 54 KB. The size limit budget is in this change rather than a later one because a single wildcard re-export silently undoes it. Navigation tracing is the SDK's own, because `remix/ui` intercepts links through the Navigation API and never touches History, so the upstream handler would emit nothing. Page loads are ordinary document loads and stay with the upstream integration. Component render errors need their own listener. The runtime funnels them into the event target `run()` returns and does not rethrow, so the global handlers never see them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
chargome
force-pushed
the
charlygomez/js-3768-add-remix-3-browser-sdk-with-a-bundled-client-entry
branch
from
September 28, 2026 16:48
f346cc4 to
8d8c83f
Compare
chargome
added this pull request to stack #24803
September 28, 2026 16:48
Contributor
size-limit report 📦
|
Member
Author
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 8d8c83f. Configure here.
This branch has not been deployed
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
1 participant
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.
Remix 3 has no bundler, so the browser gets whatever module graph the client entry reaches and nothing can be eliminated. The entry is a named export list rather than a wildcard re-export, and it is bundled once at publish time. Unbundled that costs an app 255 requests and about 364 KB gzipped; bundled it is 2 requests and 54 KB. The size budget is here rather than in a later pull request because one wildcard re-export silently undoes all of it.
Navigation tracing is the SDK's own, because
remix/uiintercepts links through the Navigation API and never touches History, so the upstream handler would emit nothing. Page loads are ordinary document loads and stay upstream.Component render errors need their own listener. The runtime funnels them into the event target
run()returns and does not rethrow, so the global handlers never see them.The
diagnostics_channelbrowser shim ships as its own file because the browser transform imports it by URL. Its subscription is dormant until that transform lands.