A while ago, I kept running into the same problem.
I wanted a client-side cache that felt solid enough for real apps — not just a quick Map wrapper, and not something locked into one data-fetching library.
Most options were either:
too minimal
too framework-specific
or not very predictable once the app got bigger
So I tried a different approach.
Instead of keeping everything in JavaScript, I moved the cache engine into Rust and compiled it to WebAssembly .
That project became Blaze Cache .
The idea
The goal was not to replace JavaScript.
The goal was to put the performance-sensitive part in a tighter core:
storage
eviction
TTL tracking
tag indexing
Then keep the TypeScript layer thin for browser integration and adapters.
After initialization, reads and writes are synchronous.…