Node-retry provides an abstraction for exponential and custom retry strategies for failed operations in Node.js. It includes helpers to generate retry timeouts, retry an operation multiple times (optionally forever), and wrap object methods so they automatically retry on failure.
Project status
- Maintenance status: GitHub updates last appear to be v0.13.1 on 2021-06-21, with the last upstream push on 2023-09-13, which is now about 2.8 years before today (2026-06-09), so the project looks quiet/dormant rather than actively maintained.
- Update cadence: The visible update history shows long gaps between updates (for example, 2016-12-12, 2018-04-09, 2021-06-21, then no newer version noted), indicating no regular release cadence.
AI summary generated
Recent updates
v0.13.1
v0.13.1 is a small bugfix release focused on retry behavior around forever mode, timeouts, and preventing problematic retry loops. The code changes include adjustments to how infinite retries are enabled, how timeout durations are computed, and how errors are preserved/managed when retry limits are hit.
v0.12.0
v0.12.0 primarily introduces an option named maxRetryTime to cap how long a retried operation may run, and it makes changes to how retry.wrap wraps object methods. The code diff also adds a new RetryOperation.reset() API and modifies retry behavior and test/packaging setup beyond what is explicitly described in the release notes.
BreakingFeaturesv0.11.0
Release v0.11.0 was published on 2018-04-09, but the publisher did not provide any release notes. No documented changes, breaking changes, fixes, or upgrade guidance are available from the provided data.
v0.10.1
Release 0.10.1 is described in the notes as adding stop functionality to the retry operation. The code diff shows additional API additions and behavioral changes beyond stop, including support for retrying forever, timer unref behavior, and a new wrapper helper.
Features0.6.0
Release 0.6.0 was published on 2014-05-26, but the publisher did not include any release notes. As a result, there is no documented information here about new features, breaking changes, bug fixes, security updates, or dependency changes, so the developer impact cannot be determined from the provided text alone.