Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
fetch implementation does not support streams from the spec - needs implementation in React Native core
See original GitHub issueReact Native has not implemented fetch on top of native APIs, and the fetch polyfill built on top of XHR does not support streams where response.body is a getter for a ReadableStream.
React Native version:
0.61.4
Steps To Reproduce
Use fetch and see that response.body is undefined rather than a getter for a ReadableStream according the the fetch spec.
Describe what you expected to happen:
I expected for response.body to be defined.
Related issues
https://github.com/facebook/react-native/issues/9629 https://github.com/facebook/react-native/issues/12912 https://github.com/github/fetch/issues/746#issuecomment-573251497 (cc @MattiasBuelens)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:16 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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 adding fetch to node.js core and the work Cloudflare, Vercel, Shopify et al are doing in WinterCG.
A spec compliant fetch also aligns with React Native’s goals IMO.
Has there been any discussion in how to bring spec compliant fetch to React Native? The polyfill fork is a good start but I’m not sure the caveats especially around performance and bundle size make it suitable for general adoption.
The Facebook GitHub org only contains project managed by Facebook. It’ll mean we have to take care of releases and everything. I’m not sure if that’s a good idea, you’ll probably be able to move faster on a separate org. What about react-native-community? @alloy can get you set up with that.