You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2019. It is now read-only.
Problem: I am using Nuxt.js which exports an extendable config for webpack. I'd like to extend "sass-loader" in that config, BUT...
The root list of module loaders contains both "vue-loader" and "sass-loader", with respective options.
Under "vue-loader" options, it contains a loaders property, which has a sub-property of sass, which contains an array of loaders, ONE of which is "sass-loader", which then, of course has a list of duplicated options for "sass-loader".
I'd like to use webpack-config to extend/merge instances of "sass-loader" wherever { loader: 'sass-loader' } is found in the entire config sub-tree. (Ideally, I would also check that the exported config doesn't have any variation between duplicate loader options.)
Can a feature be added where merging includes a deep key/value lookup of the object tree, and then merges the options at that location? Or can you think of another way to do this?
Thanks.
The text was updated successfully, but these errors were encountered:
Hello @matthew-dean, I'm really sorry that I didn't respond earlier. Better late than never.
Yes, it sould be possible.
ConfigMergeCommand.js uses simple implementation based on lodash, but it could be replaced with webpack-merge. It is designed especially for merging webpack-configs.
Problem: I am using Nuxt.js which exports an extendable config for webpack. I'd like to extend "sass-loader" in that config, BUT...
I'd like to use
webpack-config
to extend/merge instances of "sass-loader" wherever{ loader: 'sass-loader' }
is found in the entire config sub-tree. (Ideally, I would also check that the exported config doesn't have any variation between duplicate loader options.)Can a feature be added where merging includes a deep key/value lookup of the object tree, and then merges the options at that location? Or can you think of another way to do this?
Thanks.
The text was updated successfully, but these errors were encountered: