Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spread overwrites
disable: truewhen sourcemaps options providedMedium Severity
The new
disable: trueat line 45 is correctly set to prevent double debug ID injection. However,...unstable_sentryVitePluginOptionsat line 48 spreads after thesourcemapskey, so if a user passes anyunstable_sentryVitePluginOptions.sourcemapsproperty (e.g.,{ assets: ['dist/**'] }), the entiresourcemapsobject—includingdisable: true—is replaced. This silently re-introduces the double injection bug the PR aims to fix. The existing test at line 69–86 confirms this: it expectsdisableto be absent after an override.