feat(nextjs)!: Remove unstable_sentryWebpackPluginOptions - #23372
Draft
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chargome
force-pushed
the
charlygomez/js-3359-nextjs-remove-unstable_sentrywebpackpluginoptions
branch
from
August 12, 2026 14:51
675f2aa to
ab9b3a7
Compare
chargome
changed the base branch from
charlygomez/js-3355-core-add-build-time-options-for-bundler-plugin-parity
to
charlygomez/js-3358-astro-remove-unstable_sentryvitepluginoptions
August 12, 2026 14:51
Contributor
size-limit report 📦
|
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_sentryWebpackPluginOptions— both the deprecated top-level option and the one nested underwebpack.SentryBuildOptionsis hand-rolled rather than built onBuildTimeOptionsBase, so it was missingmoduleMetadataandsourcemaps.resolveSourceMap. Both were only reachable through the hatch and are added here, reusing the shared types from core.webpack.reactComponentAnnotationnow uses the sharedReactComponentAnnotationOptionstoo.Adds a build-time warning covering both spellings. This matters most for Next.js:
next.config.js/next.config.mjsget no type checking, so a removed option would otherwise be a silent no-op.Fixes #23343