The latest articles on DEV Community by Taylor Rivera (@taylorhacks). https://dev.to/taylorhacks https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210636%2F9a926339-0440-42e5-b8cf-73b02945c2bf.jpg https://dev.to/taylorhacks en Taylor Rivera Tue, 27 Oct 2026 15:47:26 +0000 https://dev.to/taylorhacks/why-i-moved-a-dashboards-state-into-sqlite-405l https://dev.to/taylorhacks/why-i-moved-a-dashboards-state-into-sqlite-405l <p>Our internal dashboard kept its state in a big React context. It worked until it didn't: every refresh re-fetched everything, and the tabs lost their place.</p> <p>I moved the state into a small SQLite database in the browser (via WASM). Now:</p> <ul> <li>Filters and tab state survive reloads</li> <li>The data layer is queryable</li> <li>The React tree got simpler</li> </ul> <p>The tradeoff is bundle size and a slightly unusual mental model. But for a tool that people use all day, persistence is worth it.</p> <p>I'm reading about SQLite internals now because I want to understand what I'm actually shipping. The documentation is surprisingly readable.</p> react sqlite frontend