Bugs in extract-text-webpack-plugin

[Timer]

• blocking

  • import() & System.import (duplicate?)
    These issues seem to break code that relies on import() and requires css, which we now support. I have not tested this, but concerning nevertheless.

• would be nice

  • css ordering
  • performance

[gaearon]

Only related to WP2? Not for 0.9 branch?

[Timer]

Only related to webpack-2 afaik, issues are tagged so and are related to wp2 features.

[gaearon]

This is worrying me. I need to start working on integrating the PWA stuff, and it seems like we'd have to backport it to 0.9.x since Webpack 2 is not ready 😞

[Timer]

I believe this never worked in WP 1 (with require.ensure), I see some older issues mentioning require.ensure.
If we don't enable performance hints (yet) we won't be bugging people to move to import(), and thus not in a worse position.

[Timer]

Full disclosure I haven't actually tested these issues to see if they're present, but since they're open, tagged, and +1'd I assume they're valid.

[gaearon]

OK I think we can live with this.

[gaearon]

At least webpack-contrib/extract-text-webpack-plugin#188 only happens in watch mode so it doesn’t affect us.

[joshwiens]

@Timer / @gaearon - Anything like this where you have blocking / aggravating bugs with something living under webpack-contrib tag me directly or @webpack-contrib/org-maintainers so we can get them on the high priority list and addressed.

[Timer]

Thanks for letting us know @d3viant0ne, we would love to see webpack-contrib/extract-text-webpack-plugin#406 fixed especially if we're going to turn on performance hints.

[joshwiens]

@Timer - On the off chance you haven't seen it, @sokra is attacking the performance problem at it's source as opposed to trying to stick a bandaid on ExtractText.

https://medium.com/webpack/the-new-css-workflow-step-1-79583bd107d7

More info as it becomes available :)

[gaearon]

Closing as stale. (Blockers have since been fixed.)