docs(remix): Add the Remix 3 alpha setup page - #19773
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Show the minimal invocation and move the optional flags into prose. The org, project and auth token are read from the environment and the release is proposed from git, so none of them need to be on the command line. Drop the troubleshooting section, that part was never shipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The command does not read the project from SENTRY_PROJECT. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
|
Rollouts skipped this pull request: Documentation-only changes (Markdown and docs site MDX files). Mention |
s1gr1d
approved these changes
Oct 2, 2026
|
|
||
| Call `init()` in your server entry. | ||
|
|
||
| Each request gets a span named after the matched route pattern. Errors thrown in route handlers, middleware and the request listener are reported. Requests the client aborted are not, and neither are thrown responses with a status from 300 to 499. Pass `shouldHandleError` to `remixV3Integration()` to change that. |
Member
There was a problem hiding this comment.
That's a callback, right?
Suggested change
| Each request gets a span named after the matched route pattern. Errors thrown in route handlers, middleware and the request listener are reported. Requests the client aborted are not, and neither are thrown responses with a status from 300 to 499. Pass `shouldHandleError` to `remixV3Integration()` to change that. | |
| Each request gets a span named after the matched route pattern. Errors thrown in route handlers, middleware and the request listener are reported. Requests the client aborted are not, and neither are thrown responses with a status from 300 to 499. Pass your custom function in `shouldHandleError` to `remixV3Integration()` to change that. |
Member
Author
There was a problem hiding this comment.
Yes but it comes with a default already
nicohrubec
approved these changes
Oct 2, 2026
1 of 6 tasks
This branch was successfully 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
3 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.
DESCRIBE YOUR PR
Adds a setup page for the Remix 3 support that
@sentry/remixships under its/v3subpaths: the--importentry that replacesremix/node-tsx, the twoinit()calls, theallowPackagesanddefineadditions to the asset server, the source map upload command, and the warning the SDK prints when the instrumentation did not apply. Marked alpha, API can change.The Remix guide's "not yet supported" alert now points to it.
Do not merge before the SDK alpha is published. SDK PRs: getsentry/sentry-javascript#24943, getsentry/sentry-javascript#24968. Refs getsentry/sentry-javascript#24687.
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-DDwith the due date. You can update this information later by editing the PR description.