will-this-react-global-state-work-in-concurrent-mode VS zustand

Exactly! The most that you can expect from Redux is not to have tearing issues with CM. On the other hand, if you are looking for an alternative library that's also event-driven and that it fully supports these kinds of features, please have a look at: https://react-rxjs.org/ .

you should check out poimandres state libraries, all three are maintained by daishi kato, which at this point is probably one of the most knowledgable devs when it comes to cm and suspense (which they also support, so you can fetch promises and async things ootb). they are either already using useMutableState via beta or use a shim. he's also made a complete test will-this-react-global-state-work-in-concurrent-mode

State Management: Zustand

For our case, points 1 and 2 can help us provide a better way of handling updates in our rapidly updating application. I have used zustand for the application.

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

Zustand

Link: https://zustand-demo.pmnd.rs/

For more code examples visit the documentation here

Have you ever wanted to learn state-management but it felt so overwhelming to get started with Redux? Or maybe you're already using Redux but don't want to take the burden anymore? If so, you might want to take a shot at Zustand! Its an amazing state management library that's easy to get started and maintain in a long run. In this post, we'll dive into creating & sharing stores with this tiny Redux alternative.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Zustand