A fast LRU (least recently used) cache for JavaScript that automatically evicts the least recently accessed items when it reaches configured limits like max item count (or max size). Useful for speeding up repeated lookups where you want bounded memory and eviction based on recent access, with optional TTL behavior that treats expired items as missing.
Project status
- Actively maintained: The GitHub source shows recent activity (last upstream push on 2026-05-27) and a sequence of tagged updates through May 2026, indicating ongoing maintenance rather than dormancy.
- Update cadence: Updates are arriving frequently (for example, 2026-05-19, 2026-05-18, 2026-05-27, plus multiple in early May), which suggests an active development rhythm up to the present date (2026-06-11), with the latest update about 2 weeks ago.
AI summary generated 2026-06-11
Recent updates
v11.5.1
2026-05-27v11.5.1 is a small patch release with no publisher release notes provided. The code diff indicates this version primarily adjusts TypeScript option typing for LRUCache fetch/memo contexts, plus version metadata updates in package.json and package-lock.json.
v11.5.0
2026-05-19This release introduces a new LRUCache option, backgroundFetchSize, which controls how much an in-flight background fetch promise counts toward cache size while it is pending. The change mainly affects calculatedSize, tracing metrics, and potentially eviction behavior during background fetches. The publisher-provided release notes were empty, so the code change details primarily come from CHANGELOG.md and the implementation.
Featuresv11.4.0
2026-05-18Release v11.4.0 was published on 2026-05-18, but the publisher did not provide any release notes. Because no change log is available, it is not possible to reliably identify new features, bug fixes, breaking changes, or security updates from the provided information.
v11.3.6
2026-05-04v11.3.6 has no published release notes. The code diff shows mostly internal refactors around performance timing support and diagnostics-channel wiring, along with packaging/build changes that introduce separate CommonJS outputs for browser and node conditions.
Breakingv11.3.5
2026-04-13Release v11.3.5 does not include any publisher-provided release notes. The code diff indicates the main change is adding a browser-specific ESM export entry (and building the corresponding browser bundle artifact), along with a version bump in package.json and package-lock.json.
Featuresv11.3.4
2026-04-13v11.3.4 introduces build and export changes to support a browser-specific ESM dialect. The release notes are missing (none provided), so the functional impact must be inferred from the code diff, which focuses on diagnostics-channel environment shims and new conditional exports/build outputs.
Featuresv11.3.3
2026-04-08Release v11.3.3 has no publisher-provided release notes. The code changes focus on how the library integrates with Node's diagnostics_channel in non-node environments, including avoiding top-level await and altering the initialization timing for the metrics and tracing channels.
Breakingv11.3.2
2026-04-06This release introduces a node-specific ESM build target (dist/esm/node) and a new diagnostics_channel adapter module, and it wires those outputs into package.json via the conditional export "node" condition. The code diff also shows updates to tracing-related test snapshots, suggesting the emitted tracing/metrics behavior may have shifted under the new diagnostics_channel integration.
Featuresv11.3.1
2026-04-06Release v11.3.1 has no publisher release notes provided. The code changes primarily affect LRUCache observability and the values placed into the `status` object (used for `lru-cache:metrics` and tracing), especially for `get` operations when a background fetch is in progress or when stale values are involved.
Breakingv11.3.0
2026-04-06The publisher did not provide release notes for v11.3.0, so there is no documented information about new functionality, fixes, or potential breaking changes. To assess upgrade risk, you will need to review the GitHub compare view for v11.3.0 vs the previous release and check for any API, configuration, or dependency changes.