Describe the bug
A query remains indefinitely in "fetching" status when the component where it is originated crashes and the error is catched by an error boundary.

To Reproduce
I've created a codesandbox to show the bug, you can see it here: https://codesandbox.io/s/loving-grothendieck-5ovgm
Steps to reproduce the behavior:

1. Go to the codesanbox;
2. Click on "Show Posts"
3. Clos

In the use-swr file, I found some effect dependencies not exhaustive, I want to konw it is correct or not.

If add eslint-plugin-react-hooks, and add "react-hooks/exhaustive-deps": "warn" in your .eslintrc It will w

I've read many similar closed issues, but haven't found a good documented solution on what can I do as a consumer of ky package if I need to support e.g iOS 10.0 browser (that breaks on async/await support currently).

I agree that it's not related to ky itself, but can be a nice help for the consumers of the package.

In our particular can we don't use babel (we use typescript), so I'm

node-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing:
https://fetch.spec.whatwg.org/#concept-http-network-fetch (see whatwg/fetch#67)

On other hand, we have a fetch-node specific extension to limit the size of the response.

My prop

Presumably these should result in a network error. The current specification doesn't state anything and it's not tested either.

See the README for instructions on where to add tests. In the specification the "blob" case of https://fetch.spec.whatwg.org/#scheme-fetch needs updating to handle current URL’s blob URL entry being null.