Skip to content

Compression in webpack-dev-server #966

Closed

Description

@frontsideair

Is there a reason that compress key is not set in WebpackDevServer config? I tried it on my machine and it made reloads faster and bandwidth usage smaller without any apparent problems.

I can send a PR if that's okay.

Activity

  1. gaearon commented on Oct 26, 2016

    @gaearon
    Contributor

    PR sounds good.

  2. added a commit that references this issue on Nov 18, 2016
  3. SpaceK33z commented on Nov 20, 2016

    @SpaceK33z
    Contributor

    Just a note that this can be closed since the PR has been merged.

  4. gaearon commented on Nov 20, 2016

    @gaearon
    Contributor

    Right. Fixed via #968, will be out in 0.8.0.

  5. added this to the 0.8.0 milestone on Nov 20, 2016
  6. cloudmu commented on Jan 9, 2017

    @cloudmu
    Contributor

    FYI, an unexpected consequence of webpack dev server compression is that Server Sent Events over proxy would be buffered, instead of proxied instantaneously.

    The issue goes away in production mode, or if I set the webpack dev server compress flag to be false in dev mode.

    I bet there are some tricks that would allow compression on without affecting Server Sent Events, but I haven't figured it out yet.

  7. don-p commented on Dec 14, 2018

    @don-p

    FYI, an unexpected consequence of webpack dev server compression is that Server Sent Events over proxy would be buffered, instead of proxied instantaneously.

    The issue goes away in production mode, or if I set the webpack dev server compress flag to be false in dev mode.

    I bet there are some tricks that would allow compression on without affecting Server Sent Events, but I haven't figured it out yet.

    This has most certainly caused problems with Server-Sent-Events. I'm using this in my project, and have determined that the gzip compression is causing the event connection to close. I'm struggling to find a way to unset this - however, it's not clear to me why this change was made, since in a development environment it's a low-impact issue to have non-compressed files served. The trade-off of making SSE unusable doesn't seem to have been a good call.

    Thanks.

  8. Timer commented on Dec 28, 2018

    @Timer
    Contributor

    Hi! Please open a new issue for this -- it's hard to track when commenting on old issues.

  9. locked and limited conversation to collaborators on Jan 8, 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

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions