- Exciting release!Introducing "safe npm". Learn more →
axios-retry-after
Advanced tools
- Version published
- Maintainers
- 1
- Weekly downloads
- 3,352
- increased by85.6%
Weekly downloads
Changelog
Readme
axios-retry-after
A tiny HTTP retry interceptor for axios.
This interceptor catches HTTP 429 errors, reads the Retry-After header, and retries the request at the proper type.
Installation
With NPM:
npm install --save axios-retry-after
With Yarn:
yarn add axios-retry-after
Example usage
import axios from 'axios'
import retry from 'axios-retry-after'
const client = axios.createClient()
client.interceptors.response.use(null, retry(client))
Customizing retry behavior
You can optionally customize the behavior of this interceptor by passing a second argument including one or more of the methods demonstrated below:
client.interceptors.response.use(null, retry(client, {
// Determine when we should attempt to retry
isRetryable (error) {
return (
error.response && error.response.status === 429 &&
// Use X-Retry-After rather than Retry-After, and cap retry delay at 60 seconds
error.response.headers['x-retry-after'] && error.response.headers['x-retry-after'] <= 60
)
}
// Customize the wait behavior
wait (error) {
return new Promise(
// Use X-Retry-After rather than Retry-After
resolve => setTimeout(resolve, error.response.headers['x-retry-after'])
)
}
// Customize the retry request itself
retry (axios, error) {
if (!error.config) {
throw error
}
// Apply request customizations before retrying
// ...
return axios(error.config)
}
}))
Keywords
FAQs
A tiny HTTP 429 Retry-After interceptor for axios
The npm package axios-retry-after receives a total of 2,665 weekly downloads. As such, axios-retry-after popularity was classified as popular.
We found that axios-retry-after demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.