Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output not generated with new chunk #300

Open
daveisfera opened this issue Nov 7, 2020 · 3 comments
Open

Output not generated with new chunk #300

daveisfera opened this issue Nov 7, 2020 · 3 comments
Labels

Comments

@daveisfera
Copy link

daveisfera commented Nov 7, 2020

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
@ztoben ztoben added the bug label Nov 9, 2020
@ztoben
Copy link
Owner

ztoben commented Nov 13, 2020

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

@daveisfera
Copy link
Author

daveisfera commented Nov 13, 2020

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
Copy link
Author

Updated to 5.4.0 and it happened there as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants