New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ambiguity in Overriding Configurations #6813
Comments
webpack-cli uses webpack-merge under the hood to extend the configuration. So the behaviour should be same as webpack-merge. |
That's not clear from the docs. The Overriding Configurations section mentions that passing the same property in the extended configuration will override the original one instead of merging the value if its an array/object. Can an example be added to explain the example of merging, using |
@cseas Yes, we would gladly accept a PR for this. |
It's there in the description of the extends option |
Feature to document
Merging arrays and objects within two webpack configs.
Congrats to the team on shipping the
extends
flag! 馃帀I went through the docs and it's not clear whether the
extends
option can be used to merge arrays and objects from two configs like we can do with the webpack-merge package.For example, is the below config going to override the
module
property of the base config completely?It's a common use-case to preserve the rules and plugins of the base config and only add to the existing rules/plugins. Example, adding one rule to Storybook's webpack config.
If this is not supported by the
extends
property, can webpack-merge or object spreading be listed as an alternative in the documentation?Use-case:
Merging two webpack configs and concatenating the objects and arrays inside them instead of overriding the base config's properties completely.
Author(s)
@burhanuday
Additional information
[ ] I am willing to work on this issue and submit a pull request.
The text was updated successfully, but these errors were encountered: