feat(react-router)!: Remove unstable_sentryVitePluginOptions - #23374
Conversation
aa5d1e9 to
2200de9
Compare
size-limit report 📦
|
2200de9 to
9fbbb98
Compare
|
bugbot run |
9fbbb98 to
e467eb0
Compare
e467eb0 to
57a4e9d
Compare
57a4e9d to
fe86f1a
Compare
fe86f1a to
4cc6f3a
Compare
ef17260 to
488405f
Compare
|
bugbot run |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 488405f. Configure here.
| // same handling as in bundler plugins: https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/05084f214c763a05137d863ff5a05ef38254f68d/packages/bundler-plugin-core/src/build-plugin-manager.ts#L102-L103 | ||
| project: Array.isArray(project) ? project[0] : project, | ||
| project, | ||
| url: sentryUrl, |
There was a problem hiding this comment.
Silent option skipped for CLI upload
Medium Severity
Top-level silent is passed through to the Vite plugin but not to the SentryCli instance that injects debug IDs and uploads source maps. After the hatch was removed, that flag no longer reaches the CLI, so upload-path logs keep printing even when silent is set.
Reviewed by Cursor Bugbot for commit 488405f. Configure here.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
488405f to
3f1ce8b
Compare
s1gr1d
left a comment
There was a problem hiding this comment.
Looks good, but there are some comments about self-hosted which seem more like part of a debugging-observation than a prominent comment we need to point out (but treat this as L, this can still be merged)
| // `url` and `headers` previously only reached the CLI through `unstable_sentryVitePluginOptions`, | ||
| // so self-hosted setups had no supported way to point this upload at their instance. |
There was a problem hiding this comment.
not sure if this comment is needed here - without looking at this PR, this feels a bit out of place


Removes
unstable_sentryVitePluginOptionsfrom the React Router build options.Net deletion of ~430 lines: the hatch could contradict
sentryOnBuildEnd, so a guard, aconsole.warnand an "explicitundefinederases the unstable value" workaround all existed purely to contain it. All three go.While removing it,
sentryUrlandheadersturned out to reach theSentryCliconstructor only through the hatch, so self-hosted setups had no supported way to point the buildEnd upload at their instance. They are now read from the top-level config — thereact-router-sourcemapse2e app depended on exactly this, viaunstable_sentryVitePluginOptions.url.Tests asserting hatch-vs-top-level precedence are deleted; the ones asserting real invariants (source maps stay disabled for the Vite plugin,
filesToDeleteAfterUploadnever forwarded,metaFrameworkpinned) are rewritten against top-level options. The #22929 regression coverage is preserved in both the unit tests and the e2e app.Fixes #23344