Breaking

• Require Node.js 20 bcae1dc
• Support modern decorators 031d770
  • Support for legacy decorators have been removed

Improvements

• Add shouldCache option (#60) 55cc5d3

v7.1.1...v8.0.0

• Add missing dependency when used with TypeScript 00faae0

v7.1.0...v7.1.1

• Allow the cache to be disabled (#49) d4dabbe

v7.0.0...v7.1.0

Breaking

• Require Node.js 14 ac4f137
• Remove cachePromiseRejection option (#48) 7a82e0f
  • Reason
  • How to cache promise rejections now

Improvements

• Allow .set() method used in the cache option to be async (#48) 7a82e0f
• Synchronously cache pending promises (#48) 7a82e0f

v6.0.2...v7.0.0

• Export missing TypeScript types (#45) aff13bb

v6.0.1...v6.0.2

• Follow-up fix to backport in 4.0.3.

v4.0.3...v4.0.4

• Backport 343ac6e from v5.

v4.0.2...v4.0.3

• Only use internal promise cache if a value already exists in cache (#32) 873390d

v6.0.0...v6.0.1

Breaking

• Remove maxAge option 19b418e
  • For a custom cache, this means instead of .set() being provided an object with the properties value and maxAge, it will only be provided value as the first argument.
  • How to preserve max age functionality.

Improvements

• The custom cache can now be async by returning a promise in the .get() and .has() cache methods
• Promises returned from a memoized function will be cached internally and take priority over cache. The promise cache does not persist outside of the current instance and properties assigned to a returned promise will not be kept. The custom cache will be provided the values of resolved promises instead of the promises themselves.

v5.0.1...v6.0.0

• Fix TypeScript type of optional custom cache (#27) 733e324

v5.0.0...v5.0.1