You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 23, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 23, 2019. It is now read-only.
One cool thing about webpack is that it allows you to output multiple bundles for production. It's not clear to me if this is even possible in the python-webpack world. If it is, some documentation would be nice, if not, it would be a great feature.
As long as webpack adds it to the list of assets emitted, it should work. There are test cases, but let me know if you have any issues.
WebpackBundle instances are a pretty thin layer on top of the compilation output, if it doesn't work to your needs, you can get the output via the instance's stats attribute.
Activity
markfinger commentedon May 18, 2015
As long as webpack adds it to the list of assets emitted, it should work. There are test cases, but let me know if you have any issues.
WebpackBundleinstances are a pretty thin layer on top of the compilation output, if it doesn't work to your needs, you can get the output via the instance'sstatsattribute.I'll leave this open as a TODO for docs
ntucker commentedon May 19, 2015
Sorry, I think I got confused about terminology. I mean chunks. Where you get several output files based on some split of the code. Aka code splitting
[-]Multiple bundles[/-][+]Chunking aka code splitting[/+]markfinger commentedon May 19, 2015
#10 is still open regarding a test case. I suspect it'll work, but I've haven't tried it yet
markfinger commentedon Jun 25, 2015
I haven't yet had a need for this, so I haven't really spent any time thinking about a workflow.
As described above, you can introspect the compilation output to pull out paths to particular assets.