Skip to content

Bugs in extract-text-webpack-plugin #1668

Closed

Description

@Timer

Activity

  1. added this to the milestone on Feb 27, 2017
  2. gaearon commented on Feb 27, 2017

    @gaearon
    Contributor

    Only related to WP2? Not for 0.9 branch?

  3. Timer commented on Feb 27, 2017

    @Timer
    ContributorAuthor

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

  4. gaearon commented on Apr 18, 2017

    @gaearon
    Contributor

    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 😞

  5. Timer commented on Apr 18, 2017

    @Timer
    ContributorAuthor

    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.

  6. Timer commented on Apr 18, 2017

    @Timer
    ContributorAuthor

    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.

  7. gaearon commented on Apr 19, 2017

    @gaearon
    Contributor

    OK I think we can live with this.

  8. gaearon commented on Apr 19, 2017

    @gaearon
    Contributor

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

  9. joshwiens commented on May 5, 2017

    @joshwiens
    Contributor

    @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.

  10. Timer commented on May 5, 2017

    @Timer
    ContributorAuthor

    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.

  11. modified the milestones: , on May 8, 2017
  12. joshwiens commented on Jun 11, 2017

    @joshwiens
    Contributor

    @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 :)

  13. gaearon commented on Jan 8, 2018

    @gaearon
    Contributor

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

  14. locked and limited conversation to collaborators on Jan 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions