Hey dev.to π
If you've read my previous post about layercache , you know it's a multi-layer caching library for Node.js β Memory β Redis β Disk behind a single get() call, with stampede prevention, tag invalidation, circuit breaking, and all the production-grade stuff you eventually need.
Today I'm releasing v1.3.3 , and it's different from all the previous releases.
No new features. No benchmark numbers. No shiny API additions.
Just nine bugs I found in my own library. I want to walk through all of them β what they were, why they happened, and what I did to fix them.
Some are embarrassing. All of them are real.
Why I did a full security audit
When you're building in the open and people start actually using the thing, you feel differently about the code.β¦