Tom Sherman

Can we expand the fix to forward all of the original headers, as is specified in the fetch standard? ref: https://github.com/whatwg/fetch/issues/553

> The metro runs when I do react-native run-ios, and the metro runs when I build from xcode. You can remove the build phase to stop this from happening. Mine...

We run the `react-native start-webpack` command manually. You can always replace that build phase with one that runs `start-webpack` instead.

One of the use cases I've been thinking about is combining do expressions with [pattern matching](https://github.com/tc39/proposal-pattern-matching) to mimic Rust's error handling. This use case would require option 2. ```javascript //...

This should be possible without introducing another component or API, instead of using async/await the component could `use(highlight())`. That's what I've done in my PR here: https://github.com/tom-sherman/react-perfect-syntax-highlighter/pull/4 (note: I created...

This may be fixed in Node 18 where Headers et al are available globally.

@neildhar I see you've mentioned this issue around making feature documentation more comprehensive. Would you be able to give a steer on what you had in mind? I'm happy to...

I am really interested in bringing spec-compliant fetch to react native. I think there's renewed interest in the OSS community and JS developers to standardise where possible as seen in...

Good points. I'm thinking more about the bindings be as spec compliant as possible - where the spec defines a JS number I think it makes sense to use a...

> Yeah `unknown` can be thought of as the type `Record` in typescript: it's guaranteed to be an object (i.e. not an array or primitive). This is not correct. `unknown`,...