valtio VS zustand

Oh.. yeah, the proxy part does look really familiar! :-)

Also, their use of promises looks interesting: https://github.com/pmndrs/valtio?tab=readme-ov-file#suspend-... -- I might borrow some ideas from that... :-)

I explored libraries like Valtio and Mitosis, but neither fit perfectly. I didn’t want to add a peer dependency for Valtio, and Mitosis didn’t work well with a shared context.

The people behind Jotai also made Zustand and Valtio:

https://github.com/pmndrs/zustand

https://github.com/pmndrs/valtio

To me it feels like Jotai has too much manual boilerplate and Valtio has a lot of "magic" that while I do like it I don't feel like it would be a good idea for a team. Zustand sits right in the middle of boilerplate-vs-magic, and is what I chose for a large project we're doing now.

As I was reading the Supabase source code for “fun”, I came across a package named Valtio.

We took inspiration from the many frameworks we worked with throughout our careers. And maybe surprisingly, Django’s ORM layer impacted our design choices and the API quite a bit. The resulting framework relies on Zod for schemas and validation and Valtio for React integration.

Valtio is like simplified MobX

Even simpler than Zustand are state-atom libraries like jotai or recoil, or proxy based ones like valtio. Here's some discussion about the differences.

There is a package developed around this proxy concept called Valtio which is available for JavaScript, React, and so on... feel free to check and star it on Github.

When Redux feels heavy, modern libraries like Zustand or Jotai offer minimalist APIs with zero boilerplate.

Managing API calls and shared data in React doesn't have to be a hassle. Dolab simplifies this process with a clean, reusable hook powered by Zustand. It's lightweight, fast, and designed for modern frontend development.

And here we come to Zustand.

Zustand: https://github.com/pmndrs/zustand

TanStack Query Zustand Jotai Context API

For client-side state, Zustand is the way to go. It's got zero boilerplate, a tiny bundle size, and a simple but powerful API that's easy to learn. You can create a store with just a few lines of code, which is pretty neat.

Zustand + Immer. I never used a state management tool because React context API was enough for me until I discovered Zustand last year. It's a simpler and straightforward alternative to Redux.

Zustand is a simple and easy-to-use state management library.

State Management with Zustand: Zustand offers a lightweight and intuitive approach to managing shared state, reducing the need for derived state or excessive memoization. It simplifies managing and updating global state without extra boilerplate.

The people behind Jotai also made Zustand and Valtio:

https://github.com/pmndrs/zustand

https://github.com/pmndrs/valtio

To me it feels like Jotai has too much manual boilerplate and Valtio has a lot of "magic" that while I do like it I don't feel like it would be a good idea for a team. Zustand sits right in the middle of boilerplate-vs-magic, and is what I chose for a large project we're doing now.