-
Notifications
You must be signed in to change notification settings - Fork 33
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
Docs request for combination with vendor chunks and or AutoDLL Plugin #18
Comments
I was wondering whether this is related to: asfktz/autodll-webpack-plugin#23 |
It is, and I researched it to attempt to do a PR to the autodll package--basically Webpack has it planned for the future to allow plugin authors to add to stats. Currently we cannot--unless I'm missing something. So the chunk created by autodll won't be in Feel free to add it to the readme as a PR. The challenge with the setup I've proposed through these tools is that no matter which way you slice it, it requires lots of setup/configuration. That's the price we pay for frameworkless flexibility vs. something like Next.js. Basically, the notes on webpack "externals" is the beginning of a Webpack Flush Chunks fyi will be renamed universal-render. I already own the npm package. There's a lot more coming out. Any help is much appreciated to bring this all together. Also note, as everything comes together under the |
There's a note added to the readme: https://github.com/faceyspacey/webpack-flush-chunks#autodllplugin If there's more you feel should be said, go for it. |
I am currently trying to add the AutoDll Plugin to my build chain as it was reported before to work with this solution. Unfortunately I had no direct success. The vendor entry point does not seem to be visible for this plugin. It just lists the default set of bootstrap + dynamic + main. But no vendor. Is there any magic trick or option to utilize?
The text was updated successfully, but these errors were encountered: