assets-webpack-plugin icon indicating copy to clipboard operation
assets-webpack-plugin copied to clipboard

Output not generated with new chunk

Open daveisfera opened this issue 5 years ago • 3 comments

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:

  1. Run webpack with assets-webpack-plugin plugin
  2. Change code so a new chunk is generated
  3. 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

daveisfera avatar Nov 07 '20 01:11 daveisfera

Sorry, having a hard time reproducing this one. What webpack version are you using?

ztoben avatar Nov 13 '20 14:11 ztoben

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?

daveisfera avatar Nov 13 '20 21:11 daveisfera

Updated to 5.4.0 and it happened there as well

daveisfera avatar Nov 13 '20 21:11 daveisfera