Skip to content
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.

Chunking aka code splitting #21

Open
ntucker opened this issue May 18, 2015 · 4 comments
Open

Chunking aka code splitting #21

ntucker opened this issue May 18, 2015 · 4 comments

Comments

@ntucker
Copy link

ntucker commented May 18, 2015

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.

@markfinger
Copy link
Owner

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.

I'll leave this open as a TODO for docs

@ntucker
Copy link
Author

ntucker commented 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

@ntucker ntucker changed the title Multiple bundles Chunking aka code splitting May 19, 2015
@markfinger
Copy link
Owner

#10 is still open regarding a test case. I suspect it'll work, but I've haven't tried it yet

@markfinger markfinger modified the milestone: v5.0 Jun 25, 2015
@markfinger
Copy link
Owner

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.

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

No branches or pull requests

2 participants