feat(webpack): remove isolatedConfig option for @nx/webpack:webpack#30910
Merged
feat(webpack): remove isolatedConfig option for @nx/webpack:webpack#30910
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
|
View your CI Pipeline Execution ↗ for commit fd6ccc7.
☁️ Nx Cloud last updated this comment at |
79109de to
20d027d
Compare
20d027d to
720c304
Compare
Coly010
approved these changes
Apr 29, 2025
720c304 to
fd6ccc7
Compare
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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 removes the
isolatedConfigoption that has been deprecated since v17. Back when it was deprecated, we had a migration to remove the option and setwebpackConfigwith a generate config file that matches the executor's built-in behavior. Now that we're removing the option, a similar migration is added to generate the config files for any projects that skipped the migration the first time.