got vs axios-retry vs retry-axios vs requestretry vs node-fetch-retry vs superagent-retry
HTTP Request Retry Libraries for JavaScript Applications
Search packages..
gotaxios-retryretry-axiosrequestretrynode-fetch-retrysuperagent-retrySimilar Packages:
HTTP Request Retry Libraries for JavaScript Applications

axios-retry, got, node-fetch-retry, requestretry, retry-axios, and superagent-retry are npm packages that add automatic retry capabilities to HTTP requests in JavaScript applications. They help developers handle transient network failures—such as timeouts, 5xx server errors, or rate-limiting—by reissuing failed requests according to configurable policies. These libraries differ in their integration approach (plugin vs. built-in), supported HTTP clients, configuration flexibility, and maintenance status.

Npm Package Weekly Downloads Trend
3 Years
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
got13,552,51714,844304 kB56 days agoMIT
axios-retry2,602,5102,00433.6 kB58a year agoApache-2.0
retry-axios709,96549957.8 kB02 months agoApache-2.0
requestretry142,61434856.5 kB112 months agoMIT
node-fetch-retry17,75097.94 kB3-MIT
superagent-retry10,28285-1010 years ago-

HTTP Request Retry Strategies in JavaScript: A Deep Dive

When building resilient web applications, handling transient network failures is non-negotiable. The packages axios-retry, got, node-fetch-retry, requestretry, retry-axios, and superagent-retry all aim to automate retry logic for failed HTTP requests — but they differ significantly in architecture, flexibility, and ecosystem alignment. Let’s examine how each approaches retries and when to use which.

🧩 Core Architecture: Standalone vs Plugin vs Built-In

axios-retry is a plugin that extends the popular axios HTTP client using its interceptor system. It doesn’t replace axios; it enhances it.

import axios from 'axios';
import axiosRetry from 'axios-retry';

axiosRetry(axios, { retries: 3 });

// Now all axios requests will retry automatically
await axios.get('/api/data');

retry-axios (often abbreviated rax) also integrates with axios, but uses a different mechanism: it wraps the request in a retry-aware function that can be applied per-call or globally.

import * as rax from 'retry-axios';
import axios from 'axios';

const interceptorId = rax.attach(); // attaches globally

// Or use per-request:
await rax(axios.get('/api/data'), { retry: 3 });

superagent-retry works similarly as a plugin for the superagent HTTP library. You call .retry() on a request chain.

import superagent from 'superagent';
import 'superagent-retry';

await superagent
  .get('/api/data')
  .retry(3) // retries up to 3 times
  .end();

node-fetch-retry wraps the native-like node-fetch API and adds retry options directly to the fetch call.

import fetchRetry from 'node-fetch-retry';

await fetchRetry('/api/data', {
  retries: 3,
  retryDelay: 1000
});

requestretry is a full replacement for the now-deprecated request library, bundling retry logic into its core API.

import request from 'requestretry';

request({
  url: '/api/data',
  maxAttempts: 3,
  retryDelay: 1000
}, (err, response, body) => {
  // handle result
});

got stands apart: retry logic is built directly into its core design. No plugins needed — retries are a first-class feature.

import got from 'got';

await got('/api/data', {
  retry: {
    limit: 3,
    methods: ['GET', 'PUT']
  }
});

⚠️ Important: The request library (and by extension requestretry) has been officially deprecated since February 2020. While requestretry still functions, it should not be used in new projects due to lack of modern maintenance and reliance on an outdated HTTP client.

🎯 Retry Configuration Granularity

How much control do you get over when and how retries happen?

got offers the most granular control. You can specify:

  • Which HTTP methods to retry
  • Which status codes trigger retries
  • Custom retry conditions via functions
  • Exponential backoff with jitter
await got('/api/data', {
  retry: {
    limit: 3,
    methods: ['GET', 'HEAD'],
    statusCodes: [408, 413, 429, 500, 502, 503, 504],
    calculateDelay: ({ attemptCount }) => Math.pow(2, attemptCount) * 1000
  }
});

axios-retry allows custom retry conditions via the retryCondition option and supports exponential backoff through retryDelay.

axiosRetry(axios, {
  retries: 3,
  retryCondition: (error) => {
    return error.response?.status === 503;
  },
  retryDelay: axiosRetry.exponentialDelay
});

retry-axios provides similar configurability, including custom retry logic and delay strategies.

await rax(axios.get('/api/data'), {
  retry: 3,
  noResponseRetries: 2,
  httpMethodsToRetry: ['GET', 'HEAD'],
  statusCodesToRetry: [[100, 199], [429, 429], [500, 599]]
});

superagent-retry is more limited — it retries on network errors and specific status codes (5xx by default), but customization requires overriding internal methods.

superagent
  .get('/api/data')
  .retry(3, [500, 502, 503]) // only these statuses
  .end();

node-fetch-retry supports basic options like retries, retryDelay, and retryOn, but lacks deep customization.

fetchRetry('/api/data', {
  retries: 3,
  retryOn: (attempt, error, response) => response?.status === 503
});

requestretry allows setting maxAttempts, retryDelay, and retryStrategy, but again, this is built on a deprecated foundation.

🔄 Backoff Strategies

All packages support some form of delay between retries, but implementation varies.

  • got: Full control via calculateDelay function; includes built-in backoff option.
  • axios-retry: Provides exponentialDelay, linearDelay, or custom functions.
  • retry-axios: Uses exponential backoff by default; configurable via currentRetryAttempt.
  • superagent-retry: Simple linear delay; no built-in exponential strategy.
  • node-fetch-retry: Accepts static retryDelay or a function (retryNumber) => delay.
  • requestretry: Supports retryDelay and retryDelayMultiplier for exponential behavior.

🌐 Ecosystem Alignment

Your choice often depends on your existing HTTP client:

  • Already using axios? → Choose axios-retry (more widely adopted) or retry-axios (more Google-centric).
  • Using superagent? → superagent-retry is your only real option.
  • Prefer native fetch? → node-fetch-retry gives you retry logic while keeping a familiar API.
  • Starting fresh or want maximum control? → got is purpose-built for robust HTTP interactions with retries as a core concern.
  • Still on request? → Migrate away; do not start new projects with requestretry.

💡 Real-World Recommendation

  • For new projects: Use got if you’re in Node.js and need maximum reliability and configurability. It’s actively maintained, modern, and retry logic is deeply integrated.
  • In an axios-based frontend/backend: axios-retry is the community standard — simple to set up and well-documented.
  • If you must use fetch: node-fetch-retry is acceptable for basic needs, but consider wrapping fetch yourself with a lightweight retry utility if requirements grow.
  • Avoid: requestretry due to its dependency on the deprecated request library. Also avoid mixing multiple retry strategies across your codebase — pick one HTTP client and stick with its retry solution.

📊 Summary Table

PackageTypeHTTP ClientCustom ConditionsBackoff ControlActive Maintenance
axios-retryPluginaxios✅✅ (predefined + custom)✅
retry-axiosWrapperaxios✅✅✅
superagent-retryPluginsuperagent⚠️ (limited)❌ (basic only)✅
node-fetch-retryWrappernode-fetch✅ (basic)✅ (simple)✅
requestretryFull clientrequest (deprecated)✅✅❌ (avoid)
gotBuilt-ingot✅ (full)✅ (advanced)✅

🔚 Final Thought

Retry logic seems simple until you’re debugging why a critical API call failed silently in production. The right tool gives you visibility, control, and confidence. If you’re already invested in an HTTP client like axios, extend it with its ecosystem’s retry package. But if you’re choosing from scratch — especially for backend services where reliability is paramount — got’s thoughtful, integrated approach makes it the strongest choice today.

How to Choose: got vs axios-retry vs retry-axios vs requestretry vs node-fetch-retry vs superagent-retry
  • got:

    Choose got if you're starting a new Node.js project and need a modern, full-featured HTTP client with retry logic built directly into its core. It offers the most granular control over retry conditions, status codes, methods, and backoff strategies, and is actively maintained with a focus on reliability and developer experience.

  • axios-retry:

    Choose axios-retry if you're already using axios and want a widely adopted, easy-to-integrate retry plugin that leverages axios interceptors. It supports custom retry conditions and built-in delay strategies like exponential backoff, making it suitable for both frontend and Node.js environments where axios is the standard HTTP client.

  • retry-axios:

    Choose retry-axios (also known as rax) if you're in a Google Cloud or TypeScript-heavy environment and need fine-grained control over axios retries, including per-request configuration and detailed status code ranges. It’s a solid alternative to axios-retry, though slightly less common in the broader ecosystem.

  • requestretry:

    Do not choose requestretry for new projects. It extends the request library, which has been officially deprecated since 2020. While it may still work, it lacks modern maintenance, security updates, and compatibility with current Node.js best practices. Migrate existing usage to alternatives like got or axios with retry plugins.

  • node-fetch-retry:

    Choose node-fetch-retry if you prefer using a fetch-like API in Node.js and need basic retry functionality without switching HTTP clients. It’s a lightweight wrapper around node-fetch that adds retry options, but lacks the advanced customization found in more specialized libraries like got.

  • superagent-retry:

    Choose superagent-retry only if your project already relies on the superagent HTTP library and you need simple retry logic. It integrates cleanly via method chaining but offers limited customization for retry conditions and backoff strategies compared to more flexible alternatives.

Similar Npm Packages to got

got is a popular HTTP request library for Node.js, designed to simplify the process of making HTTP requests while providing a rich set of features. It supports promises and async/await syntax, making it easy to work with asynchronous code. got is known for its performance, ease of use, and built-in support for advanced features like retries, timeouts, and streaming. It is an excellent choice for developers looking to make HTTP requests in a Node.js environment.

While got is a powerful option, there are several alternatives available that also provide robust HTTP request capabilities. Here are a few notable ones:

  • axios is a widely-used promise-based HTTP client for both the browser and Node.js. It offers a simple API and supports features such as interceptors, request cancellation, and automatic JSON data transformation. axios is particularly popular for frontend applications but can also be used effectively in server-side code. If you need a versatile HTTP client that works seamlessly in both environments, axios is a great choice.

  • node-fetch is a lightweight module that brings the fetch API to Node.js. It is designed to be a minimalistic and straightforward implementation of the fetch API, making it easy for developers familiar with the browser's fetch to make HTTP requests in a Node.js environment. If you prefer a simple and native-like API for making requests, node-fetch is an excellent alternative.

  • request was once a popular HTTP request library for Node.js, known for its simplicity and ease of use. However, it has been deprecated in favor of more modern alternatives like got and axios. While it is still available, it is recommended to use more actively maintained libraries for new projects.

To see how got compares with axios, node-fetch, and request, check out the comparison: Comparing axios vs got vs node-fetch vs request.

Similar Npm Packages to axios-retry

axios-retry is a popular library that enhances the functionality of Axios, a widely-used HTTP client for JavaScript. This package allows developers to automatically retry failed HTTP requests, which can be particularly useful in scenarios where network issues or server errors might temporarily prevent a request from succeeding. With configurable options for the number of retries, delay between attempts, and conditions under which to retry, axios-retry provides a robust solution for improving the reliability of API interactions in applications.

While axios-retry is a great option for adding retry functionality to Axios requests, there are alternatives available that serve similar purposes. One notable alternative is:

  • retry-axios. This library is built specifically for retrying Axios requests and offers a similar feature set to axios-retry. It provides automatic retries for failed requests, allowing developers to specify the number of retry attempts and the conditions under which retries should occur. retry-axios is designed to be simple to use and integrates seamlessly with Axios, making it an excellent choice for developers looking for an alternative to axios-retry.

For a detailed comparison of these two packages, you can check out the following link: Comparing axios-retry vs retry-axios.

Similar Npm Packages to retry-axios

retry-axios is a library that enhances the functionality of Axios, a popular HTTP client for JavaScript. It provides a mechanism to automatically retry failed HTTP requests, making it easier to handle transient errors such as network issues or server unavailability. By integrating retry logic directly into Axios, retry-axios allows developers to configure how many times a request should be retried, the delay between retries, and which types of errors should trigger a retry. This can significantly improve the resilience of applications that rely on external APIs.

While retry-axios offers a robust solution for retrying requests, there are several alternatives in the ecosystem that provide similar functionalities:

  • axios-retry is another popular library that adds retry functionality to Axios. It allows developers to specify the number of retries, the delay between retries, and conditions under which a retry should occur. axios-retry is straightforward to use and integrates seamlessly with Axios, making it a solid choice for those looking to add retry logic to their HTTP requests without much overhead.

  • fetch-retry is designed for the Fetch API, providing a similar retry mechanism for requests made using the Fetch API. This library allows developers to specify retry options, such as the number of attempts and the delay between retries. If your application uses the Fetch API instead of Axios, fetch-retry is an excellent alternative for implementing retry logic.

  • retry-request is a library that provides retry functionality for HTTP requests made with various libraries, including Axios and the native HTTP module in Node.js. It offers a flexible API for configuring retries and can be used in both browser and server environments. If you need a more generalized solution that works across different HTTP clients, retry-request might be the right choice.

  • superagent-retry is an extension for Superagent, another popular HTTP client. This library adds retry capabilities to Superagent requests, allowing developers to specify retry conditions and delays. If your project is already using Superagent, superagent-retry can easily integrate retry logic into your existing setup.

To see how retry-axios compares with axios-retry, fetch-retry, retry-request, and superagent-retry, check out the comparison: Comparing axios-retry vs fetch-retry vs retry-axios vs retry-request vs superagent-retry.

Similar Npm Packages to requestretry

requestretry is a popular npm package that enhances the functionality of the native HTTP request libraries in Node.js by adding automatic retry capabilities. It allows developers to specify retry logic for failed requests, making it easier to handle transient errors and improve the reliability of API calls. This is particularly useful when working with unstable networks or APIs that may occasionally fail. By configuring options such as the number of retries, delay between attempts, and error handling, requestretry helps ensure that applications can gracefully recover from temporary issues.

While requestretry provides robust retry functionality, there are several alternatives in the ecosystem that offer similar capabilities. Here are a few noteworthy options:

  • axios-retry is a library designed to work specifically with Axios, a popular HTTP client for JavaScript. It allows developers to add retry functionality to their Axios requests easily. With axios-retry, you can configure the number of retries, retry delays, and conditions under which a request should be retried. This makes it an excellent choice for projects already using Axios for HTTP requests.

  • got is a powerful and flexible HTTP request library for Node.js that comes with built-in support for retries. It provides a simple API and extensive features, including automatic retries for failed requests. Developers can customize retry behavior, including the number of retries and delay strategies, making got a great option for those looking for a comprehensive HTTP client with retry capabilities.

  • node-fetch-retry is an extension of the popular node-fetch library, adding retry functionality to it. It allows developers to specify retry logic for fetch requests, making it easier to handle transient errors when making HTTP calls. If you're using node-fetch and want to add retry capabilities, this package is a straightforward solution.

  • retry-axios is another library that adds retry functionality to Axios requests. It provides a simple way to configure retries, including exponential backoff strategies. This package is particularly useful for developers who want to enhance their existing Axios setup with retry capabilities without significant changes to their codebase.

  • superagent-retry is an extension for the SuperAgent library that adds retry functionality. SuperAgent is a popular HTTP request library for Node.js and browsers, and with superagent-retry, developers can easily implement retry logic for their requests. This is a good option for those who prefer using SuperAgent for their HTTP requests.

To explore how these libraries compare in terms of features and performance, check out the comparison: Comparing axios-retry vs got vs node-fetch-retry vs requestretry vs retry-axios vs superagent-retry.

Similar Npm Packages to node-fetch-retry

node-fetch-retry is a package that enhances the popular node-fetch library by adding retry functionality for failed HTTP requests. This is particularly useful when dealing with unreliable networks or APIs that may occasionally fail. With node-fetch-retry, developers can specify the number of retry attempts, delay between retries, and conditions under which retries should occur, making it a robust solution for improving the reliability of data fetching in Node.js applications.

While node-fetch-retry is a great option for adding retry logic to fetch requests, there are several alternatives in the ecosystem that provide similar functionalities. Here are a few noteworthy options:

  • axios-retry is a retry interceptor for the axios HTTP client. It allows developers to automatically retry requests that fail due to certain conditions, such as network errors or server responses that indicate a temporary issue. With axios-retry, you can easily configure the number of retries, delay intervals, and specific error conditions that trigger a retry, making it a powerful tool for enhancing the resilience of applications that rely on axios for HTTP requests.

  • fetch-retry is a simple wrapper around the native fetch API that adds retry functionality. It allows developers to specify the number of retries, delay between attempts, and conditions for retrying requests. This package is particularly useful for developers looking to enhance the native fetch API with minimal overhead while maintaining a straightforward API.

  • got is a powerful and flexible HTTP request library for Node.js that comes with built-in support for retries. It provides a rich set of features, including automatic retries on failure, timeout handling, and support for streams. If you are looking for a comprehensive HTTP client that includes retry logic along with many other advanced features, got is an excellent choice.

  • superagent-retry is a plugin for the superagent HTTP client that adds retry capabilities. It allows developers to automatically retry failed requests based on configurable conditions. If you are already using superagent in your application and need retry functionality, this plugin integrates seamlessly with the existing API.

For a detailed comparison of these packages, visit: Comparing axios-retry vs fetch-retry vs got vs node-fetch-retry vs superagent-retry.

Similar Npm Packages to superagent-retry

superagent-retry is a plugin for the SuperAgent HTTP client that adds automatic retry functionality for failed requests. This package is particularly useful for handling transient errors, such as network issues or temporary server unavailability, allowing developers to enhance the resilience of their applications. While superagent-retry provides a robust solution for retrying requests, there are several alternatives in the ecosystem that offer similar functionality. Here are a few noteworthy options:

  • axios-retry is a retry plugin for Axios, a popular promise-based HTTP client. This library allows you to automatically retry failed requests based on configurable conditions, such as status codes or network errors. If you are already using Axios for your HTTP requests, axios-retry is a seamless way to add retry logic to your requests without changing your existing code structure.
  • fetch-retry is a simple wrapper around the Fetch API that adds retry capabilities. It allows developers to specify the number of retry attempts and conditions under which to retry requests. If you prefer using the Fetch API and want to add retry logic without much overhead, fetch-retry is a straightforward solution that integrates easily with existing fetch calls.
  • got is a powerful HTTP request library for Node.js that comes with built-in support for retries. It offers a rich set of features, including automatic retries on network errors and HTTP status codes, making it a comprehensive solution for managing HTTP requests in Node.js applications. If you are building a Node.js application and need a robust HTTP client with retry capabilities, got is an excellent choice.
  • retry-axios is another plugin for Axios that provides retry functionality. It allows you to specify retry conditions and delays between attempts, giving you fine-grained control over how requests are retried. If you are looking for a more customizable retry solution for Axios, retry-axios offers a flexible approach that can be tailored to your application's needs.

To explore how superagent-retry compares with axios-retry, fetch-retry, got, and retry-axios, check out the comparison: Comparing axios-retry vs fetch-retry vs got vs retry-axios vs superagent-retry.

README for got


Got



Sindre's open source work is supported by the community.
Special thanks to:



Fame Helsinki Fame Helsinki



Depot logo
Fast remote container builds and GitHub Actions runners.









Human-friendly and powerful HTTP request library for Node.js

Downloads Install size

See how Got compares to other HTTP libraries

You probably want Ky instead, by the same people. It's smaller, works in the browser too, and is more stable since it's built on Fetch. Or fetch-extras for simple needs.

Support questions should be asked here.

Install

npm install got

Warning: This package is native ESM and no longer provides a CommonJS export. If your project uses CommonJS, you will have to convert to ESM. Please don't open issues for questions regarding CommonJS / ESM.

Got v11 is no longer maintained and we will not accept any backport requests.

Take a peek

A quick start guide is available.

JSON mode

Got has a dedicated option for handling JSON payload.
Furthermore, the promise exposes a .json<T>() function that returns Promise<T>.

import got from 'got';

const {data} = await got.post('https://httpbin.org/anything', {
	json: {
		hello: 'world'
	}
}).json();

console.log(data);
//=> {"hello": "world"}

For advanced JSON usage, check out the parseJson and stringifyJson options.

For more useful tips like this, visit the Tips page.

Highlights

Documentation

By default, Got will retry on failure. To disable this option, set options.retry.limit to 0.

Main API

Timeouts and retries

Advanced creation

Cache, Proxy and UNIX sockets

Integration

Migration guides

Got plugins

  • got4aws - Got convenience wrapper to interact with AWS v4 signed APIs
  • gh-got - Got convenience wrapper to interact with the GitHub API
  • gl-got - Got convenience wrapper to interact with the GitLab API
  • gotql - Got convenience wrapper to interact with GraphQL using JSON-parsed queries instead of strings
  • got-fetch - Got with a fetch interface
  • got-scraping - Got wrapper specifically designed for web scraping purposes
  • got-ssrf - Got wrapper to protect server-side requests against SSRF attacks

Comparison

gotnode-fetchkyaxiossuperagent
HTTP/2 support:heavy_check_mark:¹:x::heavy_check_mark::x::heavy_check_mark:**
Browser support:x::heavy_check_mark:*:heavy_check_mark::heavy_check_mark::heavy_check_mark:
Promise API:heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark:
Stream API:heavy_check_mark:Node.js only:x::x::heavy_check_mark:
Pagination API:heavy_check_mark::x::x::x::x:
Request cancelation:heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark:
RFC compliant caching:heavy_check_mark::x::x::x::x:
Cookies (out-of-the-box):heavy_check_mark::x::x::x::x:
Follows redirects:heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark:
Retries on failure:heavy_check_mark::x::heavy_check_mark::x::heavy_check_mark:
Progress events:heavy_check_mark::x::heavy_check_mark:Browser only:heavy_check_mark:
Handles gzip/deflate:heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark:
Advanced timeouts:heavy_check_mark::x::x::x::x:
Timings:heavy_check_mark::x::x::x::x:
Errors with metadata:heavy_check_mark::x::heavy_check_mark::heavy_check_mark::x:
JSON mode:heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark::heavy_check_mark:
Custom defaults:heavy_check_mark::x::heavy_check_mark::heavy_check_mark::x:
Composable:heavy_check_mark::x::x::x::heavy_check_mark:
Hooks:heavy_check_mark::x::heavy_check_mark::heavy_check_mark::x:
Issues open
Issues closed
Downloads
CoverageTBD
Build
Bugs
Dependents
Install size
GitHub stars
TypeScript support
Last commit

* It's almost API compatible with the browser fetch API.
** Need to switch the protocol manually. Doesn't accept PUSH streams and doesn't reuse HTTP/2 sessions.
¹ Requires Node.js 15.10.0 or above.
:sparkle: Almost-stable feature, but the API may change. Don't hesitate to try it out!
:grey_question: Feature in early stage of development. Very experimental.

Click here to see the install size of the Got dependencies.

Maintainers

Sindre SorhusSzymon Marczak
Sindre SorhusSzymon Marczak

These amazing companies are using Got


Segment is a happy user of Got! Got powers the main backend API that our app talks to. It's used by our in-house RPC client that we use to communicate with all microservices.

— Vadim Demedes

Antora, a static site generator for creating documentation sites, uses Got to download the UI bundle. In Antora, the UI bundle (aka theme) is maintained as a separate project. That project exports the UI as a zip file we call the UI bundle. The main site generator downloads that UI from a URL using Got and streams it to vinyl-zip to extract the files. Those files go on to be used to create the HTML pages and supporting assets.

— Dan Allen

GetVoIP is happily using Got in production. One of the unique capabilities of Got is the ability to handle Unix sockets which enables us to build a full control interfaces for our docker stack.

— Daniel Kalen

We're using Got inside of Exoframe to handle all the communication between CLI and server. Exoframe is a self-hosted tool that allows simple one-command deployments using Docker.

— Tim Ermilov

Karaoke Mugen uses Got to fetch content updates from its online server.

— Axel Terizaki

Renovate uses Got, gh-got and gl-got to send millions of queries per day to GitHub, GitLab, npmjs, PyPi, Packagist, Docker Hub, Terraform, CircleCI, and more.

— Rhys Arkins

Resistbot uses Got to communicate from the API frontend where all correspondence ingresses to the officials lookup database in back.

— Chris Erickson

Natural Cycles is using Got to communicate with all kinds of 3rd-party REST APIs (over 9000!).

— Kirill Groshkov

Microlink is a cloud browser as an API service that uses Got widely as the main HTTP client, serving ~22M requests a month, every time a network call needs to be performed.

— Kiko Beats

We’re using Got at Radity. Thanks for such an amazing work!

— Mirzayev Farid

npm-compare.com is an independent website designed to help developers choose the most suitable npm packages. We are not affiliated with npm, Inc, the official website for the npm registry. Note that npm is a registered trademark of npm, Inc. Please share your feedback via our GitHub repository. For more details, please refer to our Terms & Privacy.