Joshua Sosso

It seems this has long been an issue with react native https://github.com/facebook/react-native/issues/27741 According to the author of whatwg-fetch. The react native team would need to make their own implementation of...

Sorry, I should note that these issues I linked are specific to streamed responses, but it seems react native has long had issues with the way "Fetch" has worked in...

Btw the quick fix for this seems to be ```ts const hasBody = // react native whatwg-fetch check ((context.response as any)._bodyInit || context.response.body) && !nullBodyResponses.has(context.response.status) && context.options.method !== "HEAD"; ```...

I've opened a PR with the solution I outlined above. I tested with the latest expo starter app and everything seems to work fine. I've also created an issue in...

Unfortunately that isn't possible with the current tooling available in Flutter / Dart. To counteract this I usually end up making a bunch of shell scripts in my repos because...

Ran across this issue and wrote my own helper function to get around it. Thought I'd share here in case anyone else found it useful. ```dart String colorToHexCode(Color color, {ignoreTransparency...

@ggichure I'm willing to open a PR to add a fix for this if you'd like.

@pi0 Just curious what was the reason you marked this PR as a draft. I just wanted to check and see if I needed to change something on my end.

If anyone is looking for another alternative I ended up writing my own library https://github.com/joshmossas/event-source-plus It has the following improvements: - works in node, workers, and browsers - first class...

To go into more detail, it really depends on the server implementation. Server sent events typically are implemented as a never ending stream so `onclose` will never fire unless the...