feat(astro)!: Remove unstable_sentryVitePluginOptions - #23370
Draft
Conversation
Contributor
size-limit report 📦
|
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chargome
force-pushed
the
charlygomez/js-3358-astro-remove-unstable_sentryvitepluginoptions
branch
from
August 12, 2026 14:51
38665cc to
265e7ba
Compare
chargome
changed the base branch from
charlygomez/js-3355-core-add-build-time-options-for-bundler-plugin-parity
to
charlygomez/js-3361-sveltekit-remove-unstable_sentryvitepluginoptions
August 12, 2026 14:51
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.
Removes
unstable_sentryVitePluginOptionsfrom the Astro integration options — both the top-level option and the deprecated copy insidesourceMapsUploadOptions.Everything it exposed is reachable as a top-level build option. Adds a build-time warning, routed through Astro's integration logger.
The warning matters more here than elsewhere:
SentryOptionsintersectsRecord<string, unknown>, so TypeScript accepts any key and would otherwise leave the removal entirely silent. The key is also excluded from the generic "additional options" warning, which would wrongly tell users to move it into theirsentry.client.configfile.Fixes #23342