Advanced config

Hi, I passed the advanced config to the function ‘serverConfiguration’ as third parameter.

const { serverConfiguration } = require('universal-webpack');
const settings = require('./universal-webpack-settings');
const baseConfiguration = require('./webpack.server.config');

process.env.UNIVERSAL_WEBPACK_CSS_LOADER_V2 = true;

const configuration = (env, { mode }) =>
  serverConfiguration(baseConfiguration(env, { mode }), settings, {
      excludeFromExternals: [
        'lodash-es',
        ' ... ',
        /^some-other-es6-only-module(\/.*)?$/,
      ],
      loadExternalModuleFileExtensions: ['css', 'png', 'jpg', 'svg', 'xml'],
      silent: true,
      chunk_info_filename: 'webpack-chunks-test.json',
      development: mode !== 'production',
});

module.exports = configuration;

Is this done correctly? It seems like chunk_info_filename has no effect, because it remains the default (webpack-chunks.json). I’m not sure now, if the remain of the advanced config gets used.

[catamphetamine]

I suggest to make it more obvious in the readme.

Ok, added the clarification to the readme .

[catamphetamine]

Running webpack with the server config results in no console logging - no output, except the default lines.

Yes, it doesn’t use the plugin. Only client-side Webpack build does.

Somehow the advanced config doesn’t get passed to the plugin. I assume I try to pass the advanced config at the wrong place?

Yes, you should move those config parameters inside settings.

Does serverConfiguration accept three parameters?

No.

In general I just like to know where to pass the advanced config for the client and the server.

In the second argument.