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
[2.14.0] Async components don't get separate bundles #7795
Comments
Hmm. I may need to improve the repro. I noticed the issue with an enterprise app where there is now only one vendors bundle with everything from |
I can confirm this issue was introduced in 2.14.0 |
Should be fixed with v2.14.1 |
@pi0 just checked it in v.2.14.1 - although the situation got better - there is still one regression left - I no longer have a separate bundle for vendors, everything is getting merged to app.js. Is it an intended change? |
Versions
Reproduction
https://github.com/danielroe/webpack-async
Steps to reproduce
yarn build --analyze
- note that there is a separate async bundle for the huge dependencytwilio-video
yarn add nuxt@2.14 && yarn build --analyze
- note that there is no separate async bundleWhat is expected?
Bundle behaviour should not change in this significant of a way.
What is actually happening?
Significant performance degradation by bundling all dependencies in just five JS files (even on large sites), meaning we don't benefit from code-splitting or async dependencies.
Notes
The text was updated successfully, but these errors were encountered: