fix(remix): Match the Remix 3.0.0 package versions - #25008
Merged
Merged
Conversation
Remix 3.0.0 ships its internal packages at 1.0.0 and renames `@remix-run/ui` to `@remix-run/component`, so the orchestrion config matched nothing on the stable release. Fixes #25007 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sergical
marked this pull request as ready for review
October 2, 2026 15:24
sergical
requested review from
andreiborza,
chargome,
isaacs and
nicohrubec
and removed request for
a team
October 2, 2026 15:24
Contributor
size-limit report 📦
|
chargome
changed the title
Member
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
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 806e8c5. Configure here.
1 of 6 tasks
chargome
approved these changes
Oct 2, 2026
47 tasks
chargome
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Oct 5, 2026
## DESCRIBE YOUR PR Follow-up to #19773, which is already merged. Updates the Remix 3 alpha page for Remix 3.0.0: - The install step asks for Remix 3.0.0 or later instead of `remix@3.0.0-rc.1`. - The browser entry imports `run` from `remix/component`, since 3.0.0 renamed `@remix-run/ui` to `@remix-run/component`. Nothing else changes. The import map setup (`getScriptEntry`, `<ImportMap>`) that 3.0.0 requires is a Remix change every app makes and is documented by Remix, so it stays out of this page, which only shows the Sentry additions. The server snippet, the asset server snippet and the upload section are unchanged. Stays a draft until the SDK alpha with the 3.0.0 fix is published. Refs getsentry/sentry-javascript#25008. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.0.0 bumped
@remix-run/fetch-router,@remix-run/assetsand@remix-run/node-fetch-serverfrom 0.x to 1.0.0, and renamed@remix-run/uito@remix-run/component. Our orchestrion ranges ended at<1, so on 3.0.0 nothing was instrumented: no route names, no server errors, no debug IDs, and no render errors from the renamed runtime.The ranges now end at
<2, andrunis also matched in@remix-run/component. The client subscribes to bothrunchannels; an app has only one of them. Module paths and signatures did not change, which the e2e suite onremix@3.0.0confirms.The e2e app moves to 3.0.0. Its document now renders the entry's import map, because the 3.0.0 asset server no longer rewrites bare imports. That is a Remix change every app makes, not an SDK one.
Fixes #25007