use-immer VS zustand

The use-immer package additionally provides a useImmerReducer ****function that allows you to make state transitions via direct mutation, but under the hood creates an immutable copy using Proxies in JavaScript.

Apply useImmer to the top component state and the dream is complete.

If you want to use mutating code while ensuring that the final update is immutable, I recommend checking out useImmer (and useImmerReducer) - it uses immer to track mutations and do them immutably for you.

If you find yourself using multiple objects or in your state, it may be worth it to install a library like immer. Immer provides a proxy object, referred to as a draft, so while your code appears similar to a direct mutation of state, a copy is created under the hood when an update when immer is used.

useImmer is also pretty nice too - useReducer is definitely the way if you only want specific ways to manipulate the object though (and useImmerReducer can make writing the logic for that easier too)

Within the component itself, I used a useImmer hook for the state, as it lets me write mutating code while ensuring that the actual update is immutable - but if you're only holding your array in the useState hook, a shallow clone would work fine. js setItems(items => arrayMove([...items], ...params))

React is a lot more strict, and for what we need we cannot leave the state in individual components, we need to pull it up to the App component. Making modifications to deeply nested state is a lot of nasty code, fortunately React world has a solution - immer and its hooks version useImmer.

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

I tried using skipHydration inside my zustand store based on their docs, then rehydrating it inside my modal. So far im getting the same errors. https://github.com/pmndrs/zustand/blob/main/docs/integrations/persisting-store-data.md