fixWebpackChunksIssue() does not work with custom bundle names

[maxmilton]

Going off discussion in #142 (comment) I'm openning a dedicated issue for this.

I'm currently implementing my own logic for removing <script> tags webpack injects at runtime because it causes an async race condition.

I did see the fixWebpackChunksIssue function which would probably solve the same issue, however, the bundle name regex' are hardcoded and my bundle names are different so they don't get handled by fixWebpackChunksIssue().

Being able to customise the names might be a possible solution. This might be related to #144 since it would probably be necessary to pass a RegExp in the config.

[stereobooster]

How your Webpack chunk names look like?

[maxmilton]

Sorry, I got caught up in an important client project for a while.

In the specific case where I ran into this issue, the relevant part of my webpack config is:

output: {
    path: config.build.assetsRoot,
    filename: utils.assetsPath('js/[name].[chunkhash:7].js'),
    chunkFilename: utils.assetsPath('js/[id].[chunkhash:7].js'),
    // chunkFilename: utils.assetsPath('js/[name].[chunkhash:7].js'), // for some projects or debugging
    jsonpFunction: '$$', // default "webpackJsonp" is too long
  },

I've also worked with other webpack setups where the file naming scheme was completely different.

Is there maybe some way to extract the file names from webpack? That way any name may be possible.

[stereobooster]

I wonder if there exists some setting in Webpack, like this in HtmlWebpackPlugin

// Ensure chunks are evaluated in correct order
chunksSortMode: 'dependency'