feat(nextjs): Deprecate Webpack top-level options #18343
+442
−31
Conversation
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
RulaKhaled
approved these changes
Nov 28, 2025
Member
RulaKhaled
left a comment
RulaKhaled
left a comment
There was a problem hiding this comment.
Generally looks good to me, but i'll recommend waiting for @charly's review!
This was referenced Nov 28, 2025
…level ones for deprecation
…dd deprecation warnings for top-level options
logaretm
force-pushed
the
awad/js-1111-deprecate-top-level-webpack-options
branch
from
beb7c72 to
9ef882c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR deprecates the webpack-only configurations via the
@deprecatedJSDoc annotation and introduces a newwebpackconfig namespace for them.Under the hood the logic was changed to read from the new values, with a compatibility layer that sets them from the deprecated top-level options while warning for each option if used.
This should set us up for a v11/v12 deletion of those options.
I might have missed a few options that only affect webpack, so I appreciate a good look at this. At any case this isn't breaking so even if missed a few, users won't experience disruptions.