Hello, we are the development team of VS Code extension for debugging React Native apps (vscode-react-native). whatwg-fetch package is used in React Native lib. In our extension we debug React Native apps as a Node.js processes. Node JS global context doesn't contain DOM modules, so "exports.DOMException is not a constructor" exception is g

A bit of context, we introduced swr two weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)

We found out that swr was causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp

In the future, when Ky is more mature, we should add a comparison table to the readme. Like https://github.com/sindresorhus/got#comparison

There used to be only one type of operational error from node-fetch: FetchError.

This is no longer the case as I can count at least six: Error, NodeError, TypeError, SyntaxError, AbortError and FetchError. All of them can be triggered in one way or another through invalid response.

We would like to unify them in some ways but it's (a) a breaking change, (b) sometimes not standa

https://developers.google.com/web/updates/2017/09/abortable-fetch

Currently it is only implemented in Firefox 57 and is coming to other browsers soon.

const controller = new AbortController();
const signal = controller.signal;

setTimeout(() => controller.abort(), 5000);

fetch(url, { signal }).then(response => {
  return response.text();
}).then(text => {
  console.lo

When using getDerivedStateFromProps the lifecycle methods of react-refetch are not called.

I suppose react-refetch should be updated to use the appropriate methods.

Members that are conditionally present are hard to work with. We should just make it take several 3 string enum values or a URL and convert null and failure to 2 of those string enum values as we get a result from the header parser (the third value being the default).

I have some problem in automatic linking, it will greate this feature to add how to link this library manually to react native project. Almost every library has its guide to link packages manually.

Thanks in advance :)

The repo currently lacks an example folder where the community could see how to use the library and get started with a simple copy/paste. This folder could also be useful to (future) contributors to make sure their changes are working and didn't break anything before submitting a PR. This example folder should integrate a React.js & a React Native project, probably created with [CRA](https://g

• Create a table that lists all of the <Fetch/> props ( #162 )
• Add limitations ( #138 )
• Emphasize proper usage of doFetch() ( #153 )
• Normalization layer ( #157 )
• Advanced examples
• Throttle example

We need a new README.md that's up to date with the v2 😏

• Logo: needs better quality (now is blurry on retina display)
• CI badges 💅
• Docs section: examples & API reference
• Contributing section (CONTRIBUTING.md)
• LICENSE section