renaming entry points fixes different three.js compilations weirdly

This commit is contained in:
HF 2023-12-11 22:11:55 +01:00
parent af97cf7ec8
commit b5d48be01f

View File

@ -53,18 +53,21 @@ function buildWebpackClientConfig(
devtool: (development) ? 'inline-source-map' : false, devtool: (development) ? 'inline-source-map' : false,
entry: { entry: {
[`client.${locale}`]: client:
[path.resolve('src', 'client.js')], [path.resolve('src', 'client.js')],
[`globe.${locale}`]: globe:
[path.resolve('src', 'globe.js')], [path.resolve('src', 'globe.js')],
[`popup.${locale}`]: popup:
[path.resolve('src', 'popup.js')], [path.resolve('src', 'popup.js')],
}, },
output: { output: {
path: path.resolve('dist', 'public', 'assets'), path: path.resolve('dist', 'public', 'assets'),
publicPath: '/assets/', publicPath: '/assets/',
filename: `[name].[chunkhash:8].js`, // chunkReason is set if it is a split chunk like vendor or three
filename: (pathData) => (pathData.chunk.chunkReason)
? '[name].[chunkhash:8].js'
: `[name].${locale}.[chunkhash:8].js`,
chunkFilename: `[name].${locale}.[chunkhash:8].js`, chunkFilename: `[name].${locale}.[chunkhash:8].js`,
}, },