I Built a React State Management Library from Scratch — Here's What I Learned

I spent the last several months building Storve — a React state management library. Not because the ecosystem needed another one, but because I wanted to understand how state management actually works under the hood. Today I'm shipping it. But before I did, I built a real-time stock market simulator to stress test it. It found 3 bugs. This is the full story. Why I built it Every React project I worked on ended up with two state libraries — Zustand for client state and TanStack Query for server state. Two mental models, two sets of docs, two devtools panels. The question I kept asking: why are these separate? Loading state, error state, cached data — it's all just state. It should live in the same place as the rest of your app state. That was the idea behind Storve. What Storve is Storve is a React state management library where async state is first-class. No separate server state library. No provider wrapping your app. One createStore call covers everything. const userStore = createSto