wtf is lenstore?

LenStore is a work-in-progress state management library for JavaScript that lets you read and update application state in a clean, composable way. Instead of writing complex logic to navigate through nested objects, you describe a "path" to the data you want, and the library handles the details of getting, modifying, or setting values safely. Think of it like having a precise tool to point at any piece of your app's data. If your app tracks a user's profile inside a larger state object, you can say "give me the user's username" or "update the user's age to 23" without writing conditional checks or spread operators. The library returns an Observable, something that notifies listeners whenever that data changes, so your UI automatically re-renders when state updates. It's similar to how Redux or MobX work, but with a different mental model. Under the hood, the library uses a concept called lenses (a functional programming pattern) to create safe, composable paths through your data. A lens is like a combination of a getter and a setter for a specific location in your state tree. When you write view(L.user.username) or set(L.user.username, 'newName'), the library is using these lenses to access or modify that one piece of data while keeping the rest intact. The syntax is deliberately simple, it reads almost like accessing properties on a plain JavaScript object. This would appeal to developers building interactive web apps who find themselves writing repetitive state update code. Instead of manually deep-copying objects and updating nested fields, you describe the shape of your state once and get helper functions to work with any part of it. The project is still in active development, the README shows several planned features like combining multiple stores, middleware hooks, and special lens types for advanced patterns like references and atoms, but the core idea of a lens-based state store is already functional and ready to experiment with.