-
Notifications
You must be signed in to change notification settings - Fork 511
Extract Text Plugin does not work in child compilations #389
Comments
This actually raises an interesting question. How to associate a loader or loaders with some specific plugin? Perhaps this means there needs to be a concept of identity. webpack core already uses something known as |
Is there anything new happend recently in terms of webpack core ? How to start with this, any ideas? |
Please ask Tobias for details. |
Maybe #483, but I didn't take a deeper look at it |
So it looks like this isn't getting fixed any time soon :/ because ultimately, #483 needs webpack/webpack#4704, which contains breaking changes and therefore will wait until webpack 3. |
Any progress besides that? |
Given this is dependent on multiple |
I saw that webpack 3 is out and was wondering about the current status of this issue? |
I am still seeing this error using webpack 3.4.1. |
@PTC-JoshuaMatthews can you create minimum reproducible test repo and create new issue |
my gem 'webpacker', '~> 3.2' version, |
From jantimon/html-webpack-plugin#579
The root problem is that the extract text plugin uses kind of a hack to communicate between loader and plugin. (See here https://github.com/webpack-contrib/extract-text-webpack-plugin/blob/master/index.js#L216-L227 and here https://github.com/webpack-contrib/extract-text-webpack-plugin/blob/master/loader.js#L26)
This hack works only in the main compilation however the html-webpack-plugin is using a child compilation.
This might add a feature request for the webpack core (easier communication between loaders and plugins)
The text was updated successfully, but these errors were encountered: