async-retry vs p-retry vs promise-retry vs retry vs retry-axios
Handling Transient Failures in JavaScript Applications
Search packages..
async-retryp-retrypromise-retryretryretry-axiosSimilar Packages:

Handling Transient Failures in JavaScript Applications

These libraries provide automated retry logic for operations that might fail temporarily, such as network requests or database connections. Instead of writing manual loops or complex error handling code, developers can use these tools to define how many times an action should be repeated and how long to wait between attempts. While they share a common goal, they differ in their API style — some use callbacks, others use Promises, and one is built specifically for the Axios HTTP client.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
async-retry01,915-305 years agoMIT
p-retry01,00725.5 kB1a month agoMIT
promise-retry0318-116 years agoMIT
retry01,259-205 years agoMIT
retry-axios050464.9 kB011 days agoApache-2.0

Retry Libraries Compared: async-retry vs p-retry vs promise-retry vs retry vs retry-axios

When building reliable software, things will fail — networks drop, APIs rate-limit, and databases lock. Instead of crashing, your application should try again. These five packages solve that problem, but they approach it in different ways. Let's look at how they handle API styles, configuration, error control, and specific use cases.

🧩 API Style: Callbacks vs Promises vs Interceptors

The biggest difference is how you write your code. Modern JavaScript uses async/await, but older tools rely on callbacks.

retry uses a callback pattern. You create an operation and pass a function that accepts a callback.

const retry = require('retry');

const operation = retry.operation();

operation.attempt(function(currentAttempt) {
  fetchData(function(err, result) {
    if (operation.retry(err)) {
      return;
    }
    console.log(operation.mainError());
  });
});

async-retry wraps this logic in a Promise. You pass an async function directly.

const retry = require('async-retry');

await retry(async (bail) => {
  const result = await fetchData();
  return result;
}, { retries: 3 });

p-retry also uses Promises but focuses on standard async functions.

const pRetry = require('p-retry');

await pRetry(async () => {
  const result = await fetchData();
  return result;
}, { retries: 3 });

promise-retry passes a retry function into your Promise. You decide when to call it.

const promiseRetry = require('promise-retry');

await promiseRetry((retry, number) => {
  return fetchData().catch(retry);
}, { retries: 3 });

retry-axios is different — it attaches to an Axios instance. You do not wrap calls manually.

const axios = require('axios');
const retry = require('retry-axios');

const client = axios.create();
retry.attach({ client });

// Normal call, but retries automatically on failure
await client.get('/api/data');

⚙️ Configuration: Attempts and Delays

All libraries let you set how many times to try and how long to wait. Most use exponential backoff — waiting longer after each failure.

retry configures timeouts on the operation object.

const operation = retry.operation({
  retries: 3,
  factor: 2,
  minTimeout: 1000,
  maxTimeout: 5000
});

async-retry passes these options as the second argument.

await retry(async () => { /*...*/ }, {
  retries: 3,
  factor: 2,
  minTimeout: 1000,
  maxTimeout: 5000
});

p-retry uses a very similar options object.

await pRetry(async () => { /*...*/ }, {
  retries: 3,
  minTimeout: 1000,
  maxTimeout: 5000
});

promise-retry supports forever mode for infinite retries.

await promiseRetry((retry) => { /*...*/ }, {
  retries: 3,
  factor: 2,
  minTimeout: 1000,
  forever: false
});

retry-axios sets defaults on the Axios config object.

const client = axios.create({
  retryConfig: {
    retries: 3,
    retryDelay: 1000
  }
});

🛑 Error Handling: Aborting vs Continuing

Sometimes an error is permanent — like a 404 Not Found. Retrying won't help. You need a way to stop early.

retry requires you to check the error manually and call operation.retry(err).

operation.attempt(function(currentAttempt) {
  fetchData(function(err) {
    if (err && err.code === 'NOT_FOUND') {
      // Must manually finalize
      return operation.finalize(err);
    }
    if (operation.retry(err)) return;
  });
});

async-retry lets you call bail() to stop immediately.

await retry(async (bail) => {
  const err = await checkStatus();
  if (err && err.permanent) {
    bail(err); // Stops retries
    return;
  }
  throw new Error('Try again');
});

p-retry allows throwing specific error types to abort.

await pRetry(async () => {
  const err = await checkStatus();
  if (err && err.permanent) {
    throw new pRetry.AbortError(err); // Stops retries
  }
  throw new Error('Try again');
});

promise-retry relies on not calling the retry function.

await promiseRetry((retry) => {
  return fetchData().catch(err => {
    if (err.permanent) throw err; // Don't call retry()
    return retry(err);
  });
});

retry-axios uses a shouldRetry callback in config.

const client = axios.create({
  retryConfig: {
    shouldRetry: (err) => {
      if (err.response.status === 404) return false;
      return true;
    }
  }
});

🔌 Integration: Generic vs HTTP Specific

Some tools work for any code — database queries, file reads, or APIs. Others are built just for HTTP.

retry, async-retry, p-retry, and promise-retry are generic. They wrap any function.

// Works for DB, File, or Network
await pRetry(async () => {
  await db.query('SELECT * FROM users');
});

retry-axios only works with Axios. You cannot use it for database calls.

// Only works for Axios requests
await client.get('/users'); 
// Cannot wrap db.query() here

📊 Summary Table

Featureretryasync-retryp-retrypromise-retryretry-axios
StyleCallbackPromisePromisePromise + TriggerInterceptor
Async/Await❌ No✅ Yes✅ Yes✅ Yes✅ Yes
Abort LogicManual Checkbail()AbortErrorSkip retry()shouldRetry
ScopeGenericGenericGenericGenericAxios Only
Best ForLegacy CodeServerlessGeneral AppCustom ControlAxios Projects

💡 Final Recommendation

For most modern web applications, p-retry or async-retry are the best choices. They fit naturally into async/await code and are easy to read. If you are already using Axios for all your network calls, retry-axios saves you from wrapping every single request.

Avoid retry for new work — the callback style makes code harder to follow. Use promise-retry only if you need its unique ability to trigger retries from inside the function logic.

Pick the tool that matches your existing stack. Consistency matters more than minor feature differences.

How to Choose: async-retry vs p-retry vs promise-retry vs retry vs retry-axios

  • async-retry:

    Choose async-retry if you want a lightweight, Promise-based wrapper that is easy to read and works well in serverless environments. It is a solid choice for Next.js or Vercel projects where simplicity is key. It handles async functions cleanly without requiring extra boilerplate code.

  • p-retry:

    Choose p-retry if you are already using other utilities from the Sindre Sorhus ecosystem or need a robust, well-tested Promise library. It offers detailed error reporting through its onFailedAttempt callback. This package is ideal for general-purpose Node.js or frontend applications using async/await.

  • promise-retry:

    Choose promise-retry if you need fine-grained control over when a retry happens inside the operation itself. Unlike others that simply re-run the function, this passes a retry trigger into your code. It is often used in package managers and tools requiring specific network resilience patterns.

  • retry:

    Choose retry only if you are maintaining legacy code that relies on callbacks instead of Promises. For new projects, this library is generally not recommended because it forces you to write older-style code. It serves as the foundation for many other retry libraries but lacks modern async/await support.

  • retry-axios:

    Choose retry-axios if your project already depends heavily on Axios for HTTP requests and you want to add retry logic globally. It works as an interceptor, so you do not need to wrap individual calls. This is the most efficient option for Axios-specific workflows but cannot be used with other HTTP clients.

Similar Npm Packages to async-retry

async-retry is a utility library for retrying asynchronous functions in JavaScript. It provides a simple and flexible way to handle retries for operations that may fail intermittently, such as network requests or database operations. With async-retry, developers can easily specify the number of retries, delay between attempts, and conditions under which to retry, making it a powerful tool for improving the resilience of applications. However, there are several alternatives available that offer similar functionality. Here are a few noteworthy options:

  • p-retry is a promise-based retry utility that allows you to retry asynchronous functions with customizable options. It is designed to work seamlessly with promises, making it a great choice for modern JavaScript applications. p-retry provides a straightforward API for defining retry logic, including the number of retries, delay between attempts, and error handling. If you are looking for a lightweight and promise-centric solution for retrying asynchronous operations, p-retry is an excellent option.

  • promise-retry is another library that focuses on retrying promise-returning functions. It offers a simple API for defining retry logic, including options for maximum retries, delay, and exponential backoff. promise-retry is particularly useful for scenarios where you need to handle transient errors in asynchronous operations, such as API calls or database queries. If you prefer a library that emphasizes simplicity and ease of use, promise-retry is worth considering.

  • retry is a more general-purpose retry utility that can be used with both synchronous and asynchronous functions. It provides a flexible API for configuring retries, including options for maximum attempts, delay, and backoff strategies. retry is suitable for a wide range of use cases, making it a versatile choice for developers who need a robust retry mechanism. If you require a library that can handle both sync and async operations with customizable retry logic, retry is a solid option.

  • retry-axios is a specialized library designed to work with Axios, the popular HTTP client for JavaScript. It provides automatic retry functionality for failed HTTP requests, making it easy to handle transient errors in network communication. With retry-axios, you can configure retry options such as the number of attempts and delay between retries, all while leveraging the familiar Axios API. If you are using Axios for your HTTP requests and want to add retry capabilities, retry-axios is a great choice.

For a comprehensive comparison of these libraries, check out the link: Comparing async-retry vs p-retry vs promise-retry vs retry vs retry-axios.

Similar Npm Packages to p-retry

p-retry is a promise-based library that allows developers to retry asynchronous operations that may fail. It provides a simple and flexible way to handle retries with customizable options such as the number of attempts, delay between retries, and error handling. This can be particularly useful in scenarios where network requests or other asynchronous operations may be unreliable.

While p-retry is a great option for managing retries, there are several alternatives available in the ecosystem that offer similar functionality. Here are a few noteworthy alternatives:

  • async-retry is a library designed to retry asynchronous functions with a simple API. It allows you to specify the number of retries, the delay between attempts, and provides options for exponential backoff. async-retry is particularly useful when you need a straightforward way to handle retries in asynchronous workflows without much overhead. Its simplicity and effectiveness make it a popular choice among developers.
  • promise-retry is another library that focuses on retrying promise-based functions. It allows you to define the number of attempts and the delay between retries, and it supports customizable retry strategies. promise-retry is a good option if you want a lightweight solution specifically for promise-based operations, providing a clear and concise way to manage retries.
  • retry is a more general-purpose library that can be used to retry any function, not just promises. It provides a flexible API that allows you to specify the number of retries, delay, and custom error handling. While it can be used for asynchronous operations, its versatility makes it suitable for a wider range of use cases beyond just promises.
  • retry-axios is a specific implementation for retrying HTTP requests made with Axios. It integrates seamlessly with the Axios library, allowing you to automatically retry failed requests based on configurable options. If you are using Axios for your HTTP requests and want to add retry functionality, retry-axios is an excellent choice.

To see how p-retry compares with its alternatives, check out the comparison: Comparing async-retry vs p-retry vs promise-retry vs retry vs retry-axios.

Similar Npm Packages to promise-retry

promise-retry is a utility library that allows developers to retry asynchronous operations that return promises. This can be particularly useful for handling transient errors in network requests or other operations that may fail intermittently. By providing a simple API to specify the number of retries and the delay between attempts, promise-retry helps ensure that applications can gracefully handle failures and improve their resilience.

While promise-retry is a solid choice for retrying promises, there are several alternatives in the JavaScript ecosystem that offer similar functionality. Here are a few noteworthy options:

  • async-retry is a library designed for retrying asynchronous functions with a simple and flexible API. It allows developers to specify the number of retries, delay between attempts, and even customize the retry logic based on the type of error encountered. async-retry is particularly useful for scenarios where you need more control over the retry behavior and want to handle different types of errors differently.

  • p-retry is another lightweight library that focuses on retrying promises. It provides a straightforward API that allows you to specify the number of retries, delay, and a predicate function to determine if the operation should be retried based on the error. p-retry is a great choice for developers looking for a simple and effective way to implement retry logic in their applications without additional overhead.

  • promise-poller is a utility for polling asynchronous operations until they succeed or a specified timeout is reached. While it is not strictly a retry library, it can be used to repeatedly check the status of an operation at specified intervals. This is especially useful for scenarios where you need to wait for a resource to become available or for a condition to be met.

  • retry is a more general-purpose library for retrying functions, not limited to promises. It provides a flexible way to specify retry strategies, including exponential backoff and custom error handling. This library is suitable for developers who want a more comprehensive solution for retrying both synchronous and asynchronous operations.

  • retry-axios is an Axios interceptor that automatically retries failed HTTP requests. It integrates seamlessly with Axios, allowing developers to specify retry logic directly in their HTTP client configuration. If you are using Axios for making HTTP requests and want built-in retry functionality, retry-axios is an excellent choice.

To see how promise-retry compares with async-retry, p-retry, promise-poller, retry, and retry-axios, check out the comparison: Comparing async-retry vs p-retry vs promise-poller vs promise-retry vs retry vs retry-axios.

Similar Npm Packages to retry

retry is a versatile npm package designed to provide a simple way to retry asynchronous operations in JavaScript. This can be particularly useful in scenarios where network requests or other operations may fail intermittently and need to be retried. The retry package allows developers to specify the number of attempts, delay between attempts, and other customizable options, making it a flexible solution for handling transient errors.

While retry is a solid choice, there are several alternatives in the ecosystem that offer similar functionality with different features and approaches. Here are a few noteworthy alternatives:

  • async-retry is a lightweight library that provides a simple way to retry asynchronous functions with customizable options. It supports exponential backoff and allows you to define the number of attempts and the delay between retries. async-retry is particularly useful for handling promises and works seamlessly with async/await syntax, making it a great choice for modern JavaScript applications.

  • backoff is a library that implements exponential backoff algorithms for retrying operations. It provides a more sophisticated approach to retries, allowing developers to define custom backoff strategies. This can be particularly useful in scenarios where you want to avoid overwhelming a server with repeated requests in a short period. backoff is suitable for applications that require fine-tuned control over retry behavior.

  • promise-retry is another library focused on retrying promise-based functions. It offers a straightforward API for retrying failed promises with customizable options for the number of retries and delay. promise-retry is a good choice for developers who want a simple and effective way to handle retries in promise-based workflows.

  • retry-axios is a specialized library that integrates the retry functionality directly with the Axios HTTP client. It allows you to automatically retry failed HTTP requests made with Axios, providing a seamless experience for handling transient network errors. If you are already using Axios in your application, retry-axios can be a great addition to enhance its resilience.

  • retry-request is a library that extends the functionality of the popular request library by adding retry capabilities. It allows you to specify retry options for HTTP requests, making it easier to handle transient errors when making network calls. If you are using the request library, retry-request can provide a straightforward way to add retry logic to your requests.

To compare these packages and see how they stack up against each other, check out the following link: Comparing async-retry vs backoff vs promise-retry vs retry vs retry-axios vs retry-request.

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.

README for async-retry

async-retry

Retrying made simple, easy, and async.

Usage

// Packages
const retry = require('async-retry');
const fetch = require('node-fetch');

await retry(
  async (bail) => {
    // if anything throws, we retry
    const res = await fetch('https://google.com');

    if (403 === res.status) {
      // don't retry upon 403
      bail(new Error('Unauthorized'));
      return;
    }

    const data = await res.text();
    return data.substr(0, 500);
  },
  {
    retries: 5,
  }
);

API

retry(retrier : Function, opts : Object) => Promise
  • The supplied function can be async or not. In other words, it can be a function that returns a Promise or a value.
  • The supplied function receives two parameters
    1. A Function you can invoke to abort the retrying (bail)
    2. A Number identifying the attempt. The absolute first attempt (before any retries) is 1.
  • The opts are passed to node-retry. Read its docs
    • retries: The maximum amount of times to retry the operation. Default is 10.
    • factor: The exponential factor to use. Default is 2.
    • minTimeout: The number of milliseconds before starting the first retry. Default is 1000.
    • maxTimeout: The maximum number of milliseconds between two retries. Default is Infinity.
    • randomize: Randomizes the timeouts by multiplying with a factor between 1 to 2. Default is true.
    • onRetry: an optional Function that is invoked after a new retry is performed. It's passed the Error that triggered it as a parameter.

Authors

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.