Core CMS engine for notion-headless-cms — fetch, transform, cache with stale-while-revalidate strategy
What Framework - Origin-first ISR cache engine: stale-while-revalidate, on-demand & poll regeneration, no CDN required
Tiny async cache: TTL + LRU, single-flight dedup, and stale-while-revalidate. Zero dependencies.
WebSocket-first, stale-while-revalidate data framework for SolidJS. Data flows. UI follows.
Response-caching middleware for @ayepi/core — keyed by request + a dev-defined vary, with time (ttl/stale-while-revalidate) and space (maxBytes/maxEntries) bounds