Html-webpack-plugin: Docs should mention multiple entry chunking technique
In learning how to use webpack on a multi-entry configuration (non-SPA app), I found html-webpack-plugin to be promising for generating the script tags for all my entries. Then the main docs said all my entries would be included in the script tags for every generated html file, rendering it useless for my purposes. That is, until I found this issue report and a proposed approach:
https://github.com/jantimon/html-webpack-plugin/issues/299
https://github.com/jantimon/html-webpack-plugin/issues/299#issuecomment-216448896
The problem is that it took me an hour of scouring the web and poking around in the issue queue to find it. I suggest someone amend the docs to at least provide some pointers related to this. It might save some of your users a ton of time at the outset.
jamie-tillman
Related issues
mmjamal
路
3Comments
lonelydatum
路
3Comments
rokoroku
路
3Comments
Rowno
路
3Comments
GerkinDev
路
3Comments
Most helpful comment
That's a good idea. I'll try to do that once I feel confident I've got it figured out well enough to speak intelligently on it.
Unless Webpack is solely focused on SPAs, I do recommend that the docs do a little more to help with multiple entry configurations. The scenario I described is an inevitable progression for anyone doing a non-trivial, non-SPA Webpack config.
Expecting the dev to figure out the snarl of
All 9 comments
I haven鈥檛 used that approach by myself yet.
Maybe you can write a blog post about that topic to share how that works in detail to help others with similar requirements.
That's a good idea. I'll try to do that once I feel confident I've got it figured out well enough to speak intelligently on it.
Unless Webpack is solely focused on SPAs, I do recommend that the docs do a little more to help with multiple entry configurations. The scenario I described is an inevitable progression for anyone doing a non-trivial, non-SPA Webpack config.
Expecting the dev to figure out the snarl of