Espen Hovlandsdal

@amiller-gh Why don't you send a pull request for these changes? That sounds like a great improvement!

I'm unsure of how much impact gzip will have on SSE, since we're explicitly telling it to flush before having basically any data to work with. If gzip can somehow...

#74 would solve this for me. Any feedback on that, @dougwilson ?

This would help me as well - any feedback on this @dougwilson?

This is a great idea, thanks for shedding light on the `router.replace(router.asPath)` trick! I've asked the next.js team for clarification on the "stability" of this just to avoid implementing something...

I don't think this is a decision to be taken lightly. _Personally_, I feel that this module is not a great fit for the browser even when using polyfills for...

> We should however release this as a major update since webpack configs may need to be updated. I don't _think_ there should be any config changes necessary, but given...

> could you please take a look at approving v1.1.1 for fixing the above mentioned issue too? Do you know how I could go about doing so?

> @rexxars - I might be able to help here. If you can confirm that `v1.1.1` is not affected by this, I can update the CVE 👍 > > See:...

In general I would recommend you use a browser-oriented polyfill if that is what you need - eg https://github.com/amvtek/EventSource