Reusify helps you reuse objects and functions to improve performance in Node.js, aiming for about 10% faster execution in hot code paths. It provides a pattern for getting cached instances, resetting their state, and releasing them back to the cache to reduce function allocation and garbage collector pressure.
Project status
- Maintenance status: Evidence suggests the repo is still maintained, with an upstream push on 2026-02-09. However, the most recent tagged update shown in the provided history is v1.1.0 (2025-02-25), so activity may be occurring outside the listed release tags.
- Updates cadence: Compared to today (2026-06-09), the last upstream activity was about 4 months ago. Historically, major tags are sparse (several years between early versions), but v1.1.0 represents the latest notable update, implying more recent, ongoing development.
AI summary generated
Recent updates
v1.1.0
v1.1.0 mainly focuses on adding TypeScript support and modernizing the project tooling and CI configuration. The published code diff, however, also changes the developer toolchain (linting, testing, coverage) and adds several repository configuration files that are not mentioned in the release notes.
Featuresv1.0.4
v1.0.4 release notes only mention restoring peak performance (PR #8), but the provided code diff does not show any core library change implementing that. The changes visible in the diff are primarily README/example updates, test additions, CI configuration, and devDependency bumps.
v1.0.3
The release notes claim only documentation and benchmark updates. The actual diff shows changes limited to CI configuration, README/benchmarks, and development toolchain dependencies, with no direct changes to the library’s runtime logic.
v1.0.1
Release v1.0.1 primarily updates CI and adds code coverage reporting via Coveralls. The code diff shows new CI configuration (Travis matrix, caching, and after_script) plus new npm scripts and dev dependencies for coverage instrumentation.
SecurityFeaturesv1.0.0
This release is the initial v1.0.0 publication. There are no release-note details beyond stating it is the first release, so no specific changes, fixes, or migration guidance can be inferred.