merging loaders and making plugins unique?

OS: Win10 Node: v14.15.4

Hi there,

following the examples I have been able to merge my loaders by using mergeWithRules and I have also been able to test out mergeWithCustomize and customizeArray successfully.

However, I need to combine the two steps, as the configs I’m merging have different options for some of the plugin options.

Is this possible?

Looking at the source, I can see that mergeWithRules returns mergeWithCustomize but unable to figure out how to combine the two.

const mergedConfig = mergeWithRules(
  {
    module: {
      rules: {
        test: 'match',
        use: {
          loader: 'match',
          options: 'replace',
        },
      },
    },
  },
  { customizeArray: unique('plugins', ['HtmlWebpackPlugin'], plugin => plugin.constructor && plugin.constructor.name) }
)(commonConfig, cmsConfig, prodConfig);
module.exports = mergedConfig;

[bebraw]

I’ve found it’s easier to solve these cases through composition as that avoids the problem altogether and keeps merge simple. I see you are using HtmlWebpackPlugin so what I would do is to have it included at the most specific configuration (i.e. specifically at dev/prod/…).

Can you share your current configuration so I can propose how you could solve it this way?

[b3nk3]

It’s rather complex and I’d have to do some redactions haha.

Instead, I have sorted it based on your idea. 😃

It’s modular and only uses merge();

Thanks for your help.