Aslak Hellesøy

I suppose we could add it as a non-standard property on the `eventSourceInitDict` object. Any objections from anyone? @xv2 send a pull request and we can discuss it.

The library currently emits [Event](https://dom.spec.whatwg.org/#interface-event) for all events, but it [should be possible](https://html.spec.whatwg.org/multipage/indices.html#event-error) to emit [ErrorEvent](https://html.spec.whatwg.org/multipage/webappapis.html#errorevent) instead, which can have an `error` property. Do you want to have a go...

Could you send a PR please?

The EventSource protocol is built on top of the HTTP protocol, so if gzip is supported in HTTP (it is), that makes it implicitly supported in EventSource too, doesn't it?

@rexxars that's certainly a workaround, but it doesn't explain why the other polyfills work without this server hack. When Webpack (or Browserify) builds the polyfill, it replaces all of the...

I wouldn't trust any server side hacks to make this work. There is a bug in the code that needs to be fixed, period.

I don't have much time to maintain this library, and I am completely unfamiliar with react-native. If somebody submits a pull request with a fix I'll consider handing out commit...

Step one would be to see if we can get gherkin/go building by referencing messages from the monorepo.

Related issues: #338 #124 #205

@vinhlh would you be willing to help implement this?