Multiple bundles

[nickdima]

I have a use case where I'm using the ExtractTextPlugin for generating a css file. In this case there's an extra bundle generated for the same chunk (one js file and one css file).
Looking at the code I see that you're just taking the first element when the chunk is an array, but with my use case I would need to get access to the second item which is the css file.
The ideal option here would be to get the specific item from the array by specifying the index in the template, like this: {%=o.htmlWebpackPlugin.assets.styles[1]%} and fallback to the first item when not specifying an index.
With the current codebase this doesn't seem doable, as you just pass the data structure to the template engine.
Any thoughts? For my own use I just changed it so you always need to specify the index when the chunk is an array, but this won't work when switching back and forth between building with and without source maps.

[ampedandwired]

You can always access the underlying webpack stats object via o.webpack. So in your case you should be able to get a handle on the css using {%=o.webpack.assetsByChunkName.styles[1]%}. You'll have to manually prepend the public path though if you're using one.

The o.htmlWebpackPlugin.assets object was really only ever intended to be a bit of sugar for simple use cases - it's simply a repackaging of what's in stats.assetsByChunkName, with a few niceties such as prepending the public path for you.

I can see how exposing the all the assets as an array might be useful though. Will put some thought into how it could be handled.

[Kagami]

👍
@ampedandwired I think it would be great to include all generated stylesheets in the index.html as well in default template.

[jantimon]

The pull request #14 adds all ExtractTextPlugins to the head element

[ampedandwired]

Closing this now that #14 is merged. All generated css is now included in the default index.html, and details of the css files (per chunk and globally) are available in the htmlWebpackPlugin.files object.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.