Zustand stores a global and don't need React Context - but sometimes, it makes sense to combine them regardless.

TK Dodo is a platform dedicated to sharing insights and resources on software development, technology trends, and career growth. Through articles, interviews, and community engagement, TK Dodo empowers developers to navigate their career paths, stay updated with industry advancements, and cultivate  skills for personal and professional development.

TkDodo

Zustand is a simple and fast library for global client-state management. However, using global stores in Zustand can have drawbacks, such as difficulty initializing the store with props, complex testing, and lack of reusability. To solve these issues, React Context can be used to share the store instance while keeping the store values isolated. By combining Zustand with React Context, it becomes easier to initialize the store with props, simplify testing, and achieve component encapsulation and reusability.

Zustand and React Context

Currently using Zustand for my project, It’s so simple, Good job!

<a href="https://app.daily.dev/tkdodo" data-mention-id="oHt34Q_Zn" data-mention-username="tkdodo">@tkdodo</a> Nice article. I didn’t know you could use createStore and create inside a component. I really like it.

I’m planning to migrate from redux toolkit to zustand, is it advisable??