axios-retry vs fetch-retry vs retry-axios vs retry-request vs superagent-retry
HTTP Request Retry Libraries
Search packages..
axios-retryfetch-retryretry-axiosretry-requestsuperagent-retrySimilar Packages:

HTTP Request Retry Libraries

These libraries provide mechanisms to automatically retry failed HTTP requests in JavaScript applications. They are particularly useful for handling transient errors, such as network issues or server timeouts, ensuring that applications can recover gracefully from temporary failures. By implementing retries, developers can enhance the reliability of their applications and improve user experience by reducing the likelihood of failure due to intermittent issues.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
axios-retry02,01233.6 kB582 years agoApache-2.0
fetch-retry031755.2 kB62 years agoMIT
retry-axios050257.8 kB04 months agoApache-2.0
retry-request06916.1 kB37 months agoMIT
superagent-retry085-1010 years ago-

Feature Comparison: axios-retry vs fetch-retry vs retry-axios vs retry-request vs superagent-retry

Integration

  • axios-retry:

    axios-retry integrates directly with Axios, allowing you to add retry logic with minimal configuration. It leverages Axios interceptors to handle retries seamlessly, making it easy to implement in existing Axios-based projects.

  • fetch-retry:

    fetch-retry is designed to work with the native Fetch API, providing a simple wrapper that adds retry capabilities. It is lightweight and does not require any additional dependencies, making it a good fit for modern web applications that use Fetch.

  • retry-axios:

    retry-axios extends the functionality of Axios by providing additional features like customizable retry strategies and error handling. It is built specifically for Axios users who need more control over the retry process, allowing for advanced configurations.

  • retry-request:

    retry-request is built for the request library, making it easy to add retry functionality to Node.js applications. It is straightforward to use and integrates well with the request library's API, making it suitable for server-side applications.

  • superagent-retry:

    superagent-retry is specifically designed for SuperAgent, allowing users to add retry logic to their HTTP requests easily. It fits well within the SuperAgent ecosystem, providing a seamless experience for users of that library.

Customization

  • axios-retry:

    axios-retry allows for extensive customization of retry strategies, including the ability to specify the number of retries, delay between retries, and conditions under which retries should occur. This flexibility makes it suitable for various use cases.

  • fetch-retry:

    fetch-retry provides basic customization options, such as the number of retries and delay between attempts. However, it is less flexible compared to other libraries, focusing on simplicity and ease of use.

  • retry-axios:

    retry-axios offers advanced customization options, including exponential backoff strategies and the ability to define custom retry conditions based on response status codes or error types. This makes it a powerful choice for complex applications.

  • retry-request:

    retry-request provides basic customization options, allowing users to set the number of retries and delay. It is straightforward but lacks the advanced features found in other libraries.

  • superagent-retry:

    superagent-retry allows for some customization, including the number of retries and delay between attempts. It is designed to be simple and effective without overwhelming users with options.

Error Handling

  • axios-retry:

    axios-retry provides built-in error handling capabilities, allowing users to define specific conditions under which retries should occur. This ensures that only appropriate errors trigger a retry, improving the reliability of the application.

  • fetch-retry:

    fetch-retry has basic error handling, retrying on network errors and certain HTTP status codes. However, it may not cover all edge cases, requiring developers to implement additional logic for comprehensive error handling.

  • retry-axios:

    retry-axios excels in error handling by allowing users to specify custom conditions for retries based on response status codes and error types. This level of control helps ensure that retries are only attempted when appropriate, enhancing application stability.

  • retry-request:

    retry-request provides basic error handling, retrying on network errors and certain HTTP status codes. It is straightforward but may require additional handling for more complex scenarios.

  • superagent-retry:

    superagent-retry offers basic error handling, retrying on network errors and specific HTTP status codes. It is simple to use but may not cover all scenarios, requiring additional logic for comprehensive error handling.

Performance Impact

  • axios-retry:

    axios-retry has minimal performance impact, as it only retries failed requests without adding significant overhead. This makes it suitable for applications where performance is critical, and retries are infrequent.

  • fetch-retry:

    fetch-retry is lightweight and has a low performance impact, making it ideal for applications that prioritize speed and efficiency. However, excessive retries may still affect performance in high-load scenarios.

  • retry-axios:

    retry-axios is designed to minimize performance impact while providing robust retry capabilities. It uses efficient algorithms to manage retries, ensuring that applications remain responsive even under load.

  • retry-request:

    retry-request has a low performance impact, as it only retries failed requests. However, like other libraries, excessive retries can lead to performance degradation in high-load situations.

  • superagent-retry:

    superagent-retry is lightweight and has minimal performance overhead, making it suitable for applications where performance is a concern. It efficiently manages retries without introducing significant delays.

Learning Curve

  • axios-retry:

    axios-retry has a gentle learning curve, especially for developers already familiar with Axios. Its straightforward API and integration make it easy to implement without extensive documentation.

  • fetch-retry:

    fetch-retry is easy to learn, particularly for developers accustomed to the Fetch API. Its simplicity and minimal configuration requirements make it accessible to newcomers.

  • retry-axios:

    retry-axios may have a slightly steeper learning curve due to its advanced features and customization options. However, developers familiar with Axios will find it manageable.

  • retry-request:

    retry-request is simple to learn and implement, especially for those already using the request library. Its straightforward API allows for quick integration into existing projects.

  • superagent-retry:

    superagent-retry has a low learning curve for developers familiar with SuperAgent. Its integration is seamless, making it easy to add retry functionality without extensive setup.

How to Choose: axios-retry vs fetch-retry vs retry-axios vs retry-request vs superagent-retry

  • axios-retry:

    Choose axios-retry if you are already using Axios for making HTTP requests and need a simple way to add retry functionality without changing your existing code structure significantly. It integrates seamlessly with Axios and allows for customizable retry strategies.

  • fetch-retry:

    Select fetch-retry if you are using the Fetch API and want a lightweight solution to add retry capabilities. It is ideal for projects that prefer native browser APIs and need minimal overhead, making it a good choice for modern web applications.

  • retry-axios:

    Opt for retry-axios if you want to extend Axios with more advanced retry capabilities, including exponential backoff strategies and better error handling. This package is suitable for applications that require more control over the retry process and need to handle various error types effectively.

  • retry-request:

    Use retry-request if you are working with the request library and need a straightforward way to implement retries. It is designed for Node.js applications and is perfect for server-side HTTP requests, providing a simple API for retrying requests.

  • superagent-retry:

    Choose superagent-retry if you are utilizing the SuperAgent library for making HTTP requests and need to add retry logic. This package is tailored for SuperAgent users and provides a clean integration for retrying failed requests.

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 fetch-retry

fetch-retry is a JavaScript library that enhances the native Fetch API by adding retry functionality for failed requests. This is particularly useful when dealing with unreliable networks or APIs that may occasionally fail. With fetch-retry, developers can specify the number of retry attempts, delay between retries, and other options to ensure that their applications can gracefully handle transient errors. This library is a great choice for projects that rely heavily on the Fetch API and need robust error handling for network requests.

There are several alternatives to fetch-retry that also provide retry capabilities for HTTP requests:

  • axios-retry is a library designed to work with Axios, a popular promise-based HTTP client. It allows developers to automatically retry failed requests with configurable options, such as the number of retries and the delay between attempts. If you're already using Axios in your project, axios-retry is a natural choice to enhance your HTTP request handling with retry logic. It integrates seamlessly with Axios and provides a straightforward API for configuring retries.

  • node-fetch-retry is a retry wrapper for the node-fetch library, which is a lightweight module that brings window.fetch to Node.js. Similar to fetch-retry, node-fetch-retry allows developers to specify retry logic for failed requests made with node-fetch. This library is particularly useful for server-side applications built with Node.js that need to make HTTP requests and require robust error handling.

To see how these libraries compare, check out the comparison: Comparing axios-retry vs fetch-retry vs node-fetch-retry.

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 retry-request

retry-request is a utility library designed to enhance HTTP request capabilities by automatically retrying failed requests. It is particularly useful in scenarios where network reliability is a concern, such as in mobile applications or when interacting with unstable APIs. By implementing a retry mechanism, retry-request helps improve the resilience of applications, ensuring that transient errors do not disrupt user experience.

While retry-request provides a solid solution for retrying HTTP requests, there are several alternatives in the ecosystem that offer similar functionalities:

  • axios-retry is a popular library that integrates seamlessly with Axios, a widely-used HTTP client for JavaScript. It allows developers to automatically retry failed requests based on customizable conditions, such as specific HTTP status codes or network errors. If you are already using Axios in your application, axios-retry is a straightforward choice to add retry capabilities without significant overhead.

  • fetch-retry is a library that extends the native Fetch API to include retry functionality. It allows developers to specify retry conditions and delay intervals when making HTTP requests. If your application relies on the Fetch API and you want to add retry logic without switching to another HTTP client, fetch-retry is an excellent option.

  • requestretry is a library built on top of the popular request library for Node.js. It provides a simple way to retry HTTP requests with customizable options, including the number of retries and delay intervals. If you are working in a Node.js environment and prefer the request library, requestretry can easily enhance your request handling.

  • retry-axios is another library that adds retry functionality specifically for Axios. It is designed to be simple to use and provides options for customizing retry behavior, such as exponential backoff and retry limits. If you are looking for a robust solution for retrying requests with Axios, retry-axios is a strong contender.

  • superagent-retry is an extension for Superagent, a popular HTTP request library. It adds retry capabilities to Superagent requests, allowing developers to specify retry conditions and intervals. If you are using Superagent in your project, this library can easily integrate retry logic into your existing request handling.

To explore how these libraries compare, visit: Comparing axios-retry vs fetch-retry vs requestretry vs retry-axios vs retry-request 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 axios-retry

axios-retry

Node.js CI

Axios plugin that intercepts failed requests and retries them whenever possible.

Installation

npm install axios-retry

Usage

// CommonJS
// const axiosRetry = require('axios-retry').default;

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

axiosRetry(axios, { retries: 3 });

axios.get('http://example.com/test') // The first request fails and the second returns 'ok'
  .then(result => {
    result.data; // 'ok'
  });

// Exponential back-off retry delay between requests
axiosRetry(axios, { retryDelay: axiosRetry.exponentialDelay });

// Liner retry delay between requests
axiosRetry(axios, { retryDelay: axiosRetry.linearDelay() });

// Custom retry delay
axiosRetry(axios, { retryDelay: (retryCount) => {
  return retryCount * 1000;
}});

// Works with custom axios instances
const client = axios.create({ baseURL: 'http://example.com' });
axiosRetry(client, { retries: 3 });

client.get('/test') // The first request fails and the second returns 'ok'
  .then(result => {
    result.data; // 'ok'
  });

// Allows request-specific configuration
client
  .get('/test', {
    'axios-retry': {
      retries: 0
    }
  })
  .catch(error => { // The first request fails
    error !== undefined
  });

Note: Unless shouldResetTimeout is set, the plugin interprets the request timeout as a global value, so it is not used for each retry but for the whole request lifecycle.

Options

NameTypeDefaultDescription
retriesNumber3The number of times to retry before failing. 1 = One retry after first failure
retryConditionFunctionisNetworkOrIdempotentRequestErrorA callback to further control if a request should be retried. By default, it retries if it is a network error or a 5xx error on an idempotent request (GET, HEAD, OPTIONS, PUT or DELETE).
shouldResetTimeoutBooleanfalseDefines if the timeout should be reset between retries
retryDelayFunctionfunction noDelay() { return 0; }A callback to further control the delay in milliseconds between retried requests. By default there is no delay between retries. Another option is exponentialDelay (Exponential Backoff) or linearDelay. The function is passed retryCount and error.
onRetryFunctionfunction onRetry(retryCount, error, requestConfig) { return; }A callback to notify when a retry is about to occur. Useful for tracing and you can any async process for example refresh a token on 401. By default nothing will occur. The function is passed retryCount, error, and requestConfig.
onMaxRetryTimesExceededFunctionfunction onMaxRetryTimesExceeded(error, retryCount) { return; }After all the retries are failed, this callback will be called with the last error before throwing the error.
validateResponseFunction | nullnullA callback to define whether a response should be resolved or rejected. If null is passed, it will fallback to the axios default (only 2xx status codes are resolved).

Testing

Clone the repository and execute:

npm test

Contribute

  1. Fork it: git clone https://github.com/softonic/axios-retry.git
  2. Create your feature branch: git checkout -b feature/my-new-feature
  3. Commit your changes: git commit -am 'Added some feature'
  4. Check the build: npm run build
  5. Push to the branch: git push origin my-new-feature
  6. Submit a pull request :D
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.