
Product
Introducing Custom Pull Request Alert Comment Headers
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
superagent-retry-delay
Advanced tools
Extends the node version of superagent's Request
, adds a .retry
method
to add retrying logic to the request. Calling this will retry the request however many additional times you'd like after
a specified delay in miliseconds.
It will retry on any error condition, except for the list of response codes optionally supplied.
v2 relies on superagent's internal retry mechanism for retrying, added on superagent 3.5. Use v1 otherwise.
This library is based on superagent-retry and extends superagent
The main addition over superagent is the retry function:
/**
* @param {Number} retries
* @param {Number[] || Number} delays
* @param {Number[]} allowedStatuses
* @param {retryCallback} retryCallback
* @callback retryCallback
* @return {retry}
*/
function retry (retries, delays, allowedStatuses, retryCallback) {}
Function params:
retries
: max number of retries to attemptdelays
: delay between retries, in miliseconds. It can be either:
allowedStatuses
: list of HTTP statuses that aren't considered a failure by which we need to retryretryCallback
: this callback takes two arguments, the err, and the response
object, and must performs an evaluation on it
that must return either true
or false
. Returning false
stops any further retries.// With superagent
const superagent = require('superagent');
require('superagent-retry-delay')(superagent);
superagent
.get('https://segment.io')
.retry(2, 5000, [401, 404]) // retry twice before responding, wait 5 seconds between failures, do not retry when response is success, or 401 or 404
.end(onresponse);
superagent
.get('https://segment.io')
.retry(3, [1000, 3000, 10000], [401, 404]) // retry three times before responding, first wait 1 second, then 3 seconds, and finally 10 seconds between failures, do not retry when response is success, or 401 or 404
.end(onresponse);
superagent
.get('https://segment.io')
.retry(5, [1000, 3000], [401, 404]) // retry five times before responding, first wait 1 second, and then wait 3 seconds between all other failures, do not retry when response is success, or 401 or 404
.end(onresponse);
superagent
.get('https://segment.io')
.retry(5, [1000, 3000], [], (err, res) => {
if (res.status === 400 && res.text.includes('banana')) {
return true
}
return false;
}) // retry five times before responding, first wait 1 second, and then wait 3 seconds between all other failures, retry if code is 400 and body contains banana
.end(onresponse);
function onresponse (err, res) {
console.log(res.status, res.headers);
console.log(res.body);
}
// With supertest
const superagent = require('superagent');
require('superagent-retry-delay')(superagent);
const supertest = require('supertest');
Ensure your mocha timeout for tests (default is 2000ms) is long enough to accommodate for all possible retries, including the specified delays.
Currently the retrying logic checks for any error, but it will allow a list of status codes to avoid retrying - this is handy if you're testing say 404's.
See MIT License document.
FAQs
A retrying layer for a superagent request with delay support
The npm package superagent-retry-delay receives a total of 10,498 weekly downloads. As such, superagent-retry-delay popularity was classified as popular.
We found that superagent-retry-delay demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.
Product
Socket Fix 2.0 brings targeted CVE remediation, smarter upgrade planning, and broader ecosystem support to help developers get to zero alerts.