fix(webpack): config migrations should account for different configurations #14672
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 fixes an issue where different configurations (e.g.
deveopment
andproduction
) can mess up migrations between@nrwl/webpack
and@nrwl/react
.For example,
@nrwl/react
migrates a customwebpack.config.js
correctly, but now@nrwl/webpack
looks at the options, which is like this:And for
production
configuration, the newisolatedConfig
flag is not set, and there is a customwebpackConfig
so@nrwl/webpack
performs a migration that isn't needed.The fix is make sure we keep track of the default options, and if the default options need to be migrated, then other configurations may also need to be migrated. If the default options do not need a migration, then skip the rest of the configurations.
Notes
main.tsx
needs to be on default options, because each configuration will likely not provide a differentmain
option.options
field for default options, or<configurationName>
for things likedevelopment
andproduction
.beforeEach
.