redux VS zustand

Because the application is shared between server and browser, state is as well. If your app has a single source of state as is often the case with Redux, for example, sharing state between server and browser can be as simple as passing your state object through JSON.stringify() then adding it to a

Redux Documentation: The official Redux documentation covers everything you need to know about using Redux with React.

Next.js documentation on data fetching and state Next.js documentation on server components Redux documentation Next.js Redux Wrapper documentation

You should start with http://redux.js.org/ and learn basics such as actions, reducer, state

Redux documentation:

Use a centralized state management solution As your React application grows, it becomes difficult to manage state across multiple components. One way to solve this problem is by using a centralized state management solution such as Redux or MobX. Redux is a popular library for managing application state in React. It provides a single store that holds the entire state of the application, and a set of rules for how the state can be updated. With Redux, you can easily share state between components and manage complex state interactions. MobX is another state management library for React that uses observable data structures to manage state. It provides a more lightweight solution compared to Redux, and is especially useful for managing complex state interactions in large applications.

Website: https://redux.js.org/

Recoil was created to provide an alternative to Redux which is another popular state management library for React. In today's adventure, we will see what Recoil is, how it works, why you might want to use it in your React apps and much more..

createGlobalSize also belongs to react-use and it provides a way for you to create a global state that can be shared across multiple components without having to go for state management libraries like redux.

Redux

For global state, Zustand or RTK

zustand is really good and easy to learn. I don't use redux anymore.

Zustand is like simplified Redux

Redux is also not ideal to start with. It has great features, but can be difficult to learn at first. Zustand is a simpler library that has many similar concepts. I'd recommend it as a starting point before learning Redux.

Redux seems to mostly be used at large companies that already have Redux deeply embedded in their stack. I would not recommend learning Redux in 2023. I don't think it's the future. Context API is all you need for most projects. At my company we don't even use Context API (where possible). We just use zustand! https://zustand-demo.pmnd.rs/

I feel like zustand internal still use hooks at some point: https://github.com/pmndrs/zustand/blob/main/src/context.ts

In 1.0.0 version of zustand, it's still relatively simple: https://github.com/pmndrs/zustand/tree/v1.0.0

Initially, I used zustand as a lightweight state management library, but eventually replaced it with React's Context, which was deemed sufficient. This decision was based on a policy of minimizing global state, which has not caused much pain.

Alternatively you can setup shared state either via Context or a state management lib like zustand or jotai:

I work with React (NextJS) and from working on things in Vue, and Nuxt - the one thing I absolutely hate about React is state management. If you have never used Pinia[0] (Vuex) with Vue, it's just so, so, so much easier.

I'm using Zustand[1] with React as it is as similar as I can find to Pinia, but the whole hook system is just painful to work with... OK rant over.

I haven't built anything substantial with Svelte, but it's definitely on the radar, and I like how similar it is to Vue single file components (SFC). Hoping state management will be as nice to work with as Pinia is with Vue.

[0] https://pinia.vuejs.org/

[1] https://github.com/pmndrs/zustand