monocle-ts VS jotai

You may be interested also in checking out the implementation of Lens in monocle-ts, one of the libraries in the fp-ts ecosystem

For anyone - anyone who's faffed around with JavaScript's spread syntax when working with nested immutable data, anyway - struggling to understand the general concept or utility of lenses, I'd encourage looking into monocle-ts. The motivation [0] that kicks off the README instantly made me a believer, and TypeScript's idiosyncratic type system makes using the library remarkably natural; it fits right in without needing to deal with anything analogous to Template Haskell.

[0] https://github.com/gcanti/monocle-ts#motivation

You could have a look at the monocle-ts library. It was designed to deal with this kind of problem.

spectacles-ts integrates seamlessly with the fp-ts ecosystem (it's built on top of the excellent monocle-ts library)

lenses help with this quite a bit, check out monocle-ts

The accounts manager is responsible for storing and managing all the accounts that users have used on your app. You can use any state management solution such as Redux, Zustand, Jotai, React Context etc.

Most impactful has been reworking our data model layer and state management system. The original codebase had evolved to keep much of its business logic inside jotai atoms, and we generally had very little abstraction in the model layer. This made the model layer code complex, rigid, and bug-prone.

For atoms, Jotai or Zedux

You should try https://jotai.org/, its like riverpod

To simplify the process of defining and using global state, third-party libraries like Jotai can be useful. With Jotai, you can easily share state between components without relying on prop drilling or context propagation.

Before we proceed you can check the project on github. This implementation is for learning purposes, for production use check Jotai or Recoil.

My preferred state manager is jotai, so here's a quick example.

Jotai is like simplified Recoil

Atomic libraries like Recoil, Jotai, and Zedux specialize in expressing these dependencies clearly, giving you insight into your dependency graph and offering tools like evaluation tracing, time travel, and DI overrides to improve testability and discoverability of your code.

After Zustand, if you need anything more, I'd either go back to Redux or learn Jotai, an atomic library that's a little more powerful than Zustand. Atoms are a little more advanced, so I wouldn't start there. Though (full disclosure) I am the author of another atomic library that is aiming to make atoms simpler to learn and use. Someday we'll get there, but for now I'd say Zustand is the best place to start.