@zeit/fetch-retry
A layer on top of `fetch` (via [node-fetch](https://www.npmjs.com/package/node-fetch)) with sensible defaults for retrying to prevent common errors.
@zeit/fetch-retry@5.0.1 was published on 2020-10-14. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All @zeit/fetch-retry versions · Permanent reference to 5.0.1
Package specifications
| Version | 5.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2020-10-14T21:32:50.477Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 10.68 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @zeit/fetch-retry 5.0.1
npm install @zeit/fetch-retry@5.0.1 pnpm add @zeit/fetch-retry@5.0.1 yarn add @zeit/fetch-retry@5.0.1
Runtime dependencies
- debug ^3.1.0
- async-retry ^1.3.1
Peer requirements
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- async-retry@1.3.3 — direct
- debug@3.2.7 — direct
- ms@2.1.3 — indirect
- retry@0.13.1 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- https://registry.npmjs.org/%40zeit%2Ffetch-retry/5.0.1 — retrieved 2026-10-29T14:46:37.786Z
- https://api.deps.dev/v3/systems/npm/packages/%40zeit%2Ffetch-retry/versions/5.0.1 — retrieved 2026-10-29T14:46:38.310Z
- https://api.deps.dev/v3/systems/npm/packages/%40zeit%2Ffetch-retry/versions/5.0.1:dependencies — retrieved 2026-10-29T14:46:38.349Z