Jan Amann

It's working, but the handling of runtime errors doesn't quite work. The overlay is never shown and the app doesn't recover. I made a [fork of react-hot-boilerplate](https://github.com/amannn/react-hot-boilerplate) that uses webpack-hot-middleware....

Hi @qwertvasilii, thanks for bringing this up. [I'm aware of this](https://github.com/molindo/react-apollo-network-status/pull/18#discussion_r336864693), but I didn't work on the fix yet. I'll see if I can provide a fix after the 3.0...

Not yet, I'm not sure yet what the best solution for this is. The issue is basically this: For a given component tree we append [a link that receives all...

There's a reproduction for this issue in https://github.com/molindo/react-apollo-network-status/issues/36. Thanks to @github0013!

Hey @andrewmtam and thank you for your PR! Sure, sounds good! Would you mind to bump the React peer dependency to 18 while you're at it?

Closed in favour of https://github.com/molindo/react-apollo-network-status/pull/51.

Hmm, I'm not sure if this library is in a good position to detect this. As mentioned in the blog article you have to set up event handlers on the...

Hi @sohara and thanks for the report, hmm, no – that's the first time I hear this. Isn't this what I'm doing here as well? https://github.com/amannn/next-client-script/blob/de5ed6ffc9284e436764da076396515f13e859fe/packages/example/src/pages/index.client.tsx#L1 Would you be interested...

Hmm, interesting. Thanks for the report though. I'm currently not affected by this issue, so I'll leave it open for now in case someone else wants to look into it.

Hello @markpinero, that's a good idea. Currently you should be able to configure a wildcard to match all pages, but only one client script will be injected at a time....