memoize-fs - npm Package Versions

4.1.1 (2024-12-20)

• build: fix build

4.1.0 (2024-12-20)

• feat: cache hit check (#312)

4.0.1 (2024-12-20)

• fix: reusable variables are serialized incorrectly (#307)

4.0.0 (2024-06-20)

• BREAKING CHANGE: The maxAge option now ensures that the cache becomes invalid after the specified cache lifetime is reached based on stats.mtimeMs (last modification time of the cache file) instead of relying on an in memory timeout that invalidates the cache. This ensures that cache life times are evaluated correctly between multiple processes.

How to upgrade

If you are using the maxAge option, ensure that you add the option to every memoizer.fn call (if you have multiple) to reliably check cache validity. Most probably this is already the case in your application, and you don't need to change anything.

3.0.4 (2024-03-06)

• style: improve typing by using Awaited instead of our custom EnsurePromise type

3.0.3 (2024-03-03)

• fix: void 0 build issue
• fix: do not minify (mangle) identifiers in bundle
• fix: do not bundle meriyah dependency

3.0.2 (2024-03-01)

• fix: importing fails with moduleResolution set to node16

3.0.1 (2024-03-01)

• fix: instead of Promise<Promise<T>>, return Promise<T>

3.0.0 (2023-02-20)

• BREAKING CHANGE: drop support for node < 18
• BREAKING CHANGE: memoize-fs is now an esm module
• BREAKING CHANGE: stricter types (see dist/index.d.ts)