Releases: grischaerbe/cacheables
Releases · grischaerbe/cacheables
v2.0.0
What's Changed
- Fix: handle promise rejection and clear pending promise by @hodlen in #8.
- Hybrid module: ESM and CommonJS – as moving from a pure CommonJS to a hybrid-distributed library does not come without upgrading headaches, I consider this a breaking change.
New Contributors
Full Changelog: v1.2.2...v2.0.0
v1.2.2
Features 🎉
- Adds an option maxAge to the cache policy stale-while-revalidate to treat a cache as fresh for a certain amount of time and update in the background is maxAge is reached.
v1.1.2
README
- No e-notation in large numbers in README and JSDocs
v1.1.1
- Modified the README to not include top-level await.
- Added size-limit to devDeps
Full Changelog: v1.1.0...v1.1.1
v1.1.0
Features 🎉
- Support for different cache policies – the former approach was implicitly
cache-only
ormax-age
.
Under the hood
- Major refactoring.
- More tests.
Breaking changes 🙀
- As the cache policies are a new feature the API slightly changed.
- As the concept of
misses
became unstable and hard to maintain with different cache policies, I dismissed it. Please update your application if it's is depending on the logs of misses. (hits
are still a thing…). It might get a new chance at some point though.
v0.3.2
Misc
- README: Better example (same as quickstart)
v0.3.1
Misc
- Added a codesandbox.io quickstart to the README
v0.3.0
Features
cache.isCached(key)
returns whether a cacheable is present and valid (i.e., did not time out)- No more
setTimeout
, therefore less memory leak potential, no cleanup necessary - Tests now also include timing edge cases
v0.2.2
- Build shielt
v0.2.1
- Auto publish to npm