assets-webpack-plugin
assets-webpack-plugin copied to clipboard
Output not generated with new chunk
Describe the bug
If the code changes in a significant way (running yarn install is the easiest way to reproduce this) and a new chunk is generated, then the output is not generated with that new list of entrypoints
To Reproduce Steps to reproduce the behavior:
- Run webpack with
assets-webpack-pluginplugin - Change code so a new chunk is generated
- Notice that output hasn't updated and still lists chunks that don't exist
Expected behavior Output would be generated when a new chunk is generated
Webpack Config
{
cache: { type: 'filesystem' },
mode: 'development',
optimization: {
minimize: false,
chunkIds: 'named',
runtimeChunk: 'single',
splitChunks: {
chunks: 'all',
maxInitialRequests: 30,
maxAsyncRequests: 30,
},
},
parallelism: 4
plugins: [
new webpack.ProgressPlugin(),
new CleanWebpackPlugin(),
new AssetsWebpackPlugin({ entrypoints: true }),
],
devtool: 'source-map',
target: 'web',
watch: true,
}
Desktop (please complete the following information):
- OS: macOS 10.15.7
- Node version: 12.18.4
- Plugin version: 6.0.4
Sorry, having a hard time reproducing this one. What webpack version are you using?
We're using webpack 5.1.0 and is there any other info or logs that I can provide to help diagnose the cause of the issue?
Updated to 5.4.0 and it happened there as well