fetch icon indicating copy to clipboard operation
fetch copied to clipboard

Opinionated `fetch` (with retrying and DNS caching) optimized for use with Node.js

Results 16 fetch issues
Sort by recently updated
recently updated
newest added

https://github.com/zeit/fetch/blob/53ee6c5bf02a5dd261a6ce4df0f687fa32c2b4d1/index.js#L57-L59 It should only create one agent per protocol.

bug

Right now it's not clear than you can just do `require('@zeit/fetch')()` and that `require('@zeit/fetch')(require('node-fetch'))` isn't necessary. The readme should explain this a little better.

bug
help wanted
good first issue

Right now it's 200, which is good for many use cases, but overkill for others. As an example, if you write a little utility that abstracts over `fetch`, and someone...

enhancement

I think the current one is too high (socket timeout I believe). I think maybe 5s would be a good timeout?

enhancement
question

Hello, thanks for providing this handy fetch replacement. I wanted to provide feedback based on our usage of the lib. We were recently surprised to discover, that fetch-retry also retries...

We will be **archiving this repository** in favor of fetch in Node.js. Existing versions will **not be deprecated and can be continued to be used**. This project has worked well,...