Add Option for Post-Extract Processing about extract-text-webpack-plugin HOT 2 CLOSED

Interesting, I've never seen the syntax @import (reference) "../_style/index"; before. Is this documented somewhere?

Edit: My bad, it's documented here.

I still can't fully utilize Less' extend feature, though (like &:extend(.common); where .common is defined in an imported file).

I can see why you don't want to implement this. I'm using style-loader during development and it would be quite weird when the result differed. To be honest, currently this is not a pain point for me, my stuff works as it is. This is just optimization.

Would it be possible to implement something like a "CssCollector" plugin, which collects all CSS requires/imports, concats them and processes them together? (When one CSS file changes, it would need to process all files again, so cache-ablity is lost, but in general CSS processing is quite fast and the raw files could be cached in memory.) I might be interested in implementing something like this in the future.

from extract-text-webpack-plugin.

I thought about it and concluded that I won't add it. The reason for this is that a ExtractTextPlugin build should behave equal to a style-loader build and this is not possible with Post-Extract Processing.
Post-Extract Processing is also bad for build performance as we cannot cache idividual modules anymore.

You can use @import (reference) to avoid that stuff is imported twice.

from extract-text-webpack-plugin.