zustand vs formik vs jotai vs mobx vs react-query vs recoil vs redux vs xstate
State Management and Data Fetching Solutions for React Applications
Search packages..
zustandformikjotaimobxreact-queryrecoilreduxxstateSimilar Packages:

State Management and Data Fetching Solutions for React Applications

formik, jotai, mobx, react-query, recoil, redux, xstate, and zustand are libraries that address different aspects of state management and data synchronization in React applications. While formik specializes in form state and validation, react-query focuses on server-state management including caching, background updates, and request deduplication. The remaining libraries — jotai, mobx, recoil, redux, xstate, and zustand — provide varying approaches to managing client-side application state, ranging from global stores (redux, zustand) to fine-grained reactivity (mobx, jotai, recoil) and explicit state machines (xstate). Each library makes different trade-offs between simplicity, scalability, performance, and conceptual model.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
zustand23,036,32757,14895 kB5a month agoMIT
formik034,386585 kB8364 months agoApache-2.0
jotai021,019517 kB38 days agoMIT
mobx028,1824.35 MB865 months agoMIT
react-query048,6372.26 MB1483 years agoMIT
recoil019,5272.21 MB3223 years agoMIT
redux061,437290 kB432 years agoMIT
xstate029,2682.25 MB16314 days agoMIT

State Management Deep Dive: Formik, Jotai, MobX, React Query, Recoil, Redux, XState, and Zustand

Managing state in React apps isn’t one-size-fits-all. Some libraries handle form inputs, others sync with servers, and the rest organize your app’s internal data. Let’s compare these eight tools by how they solve real problems.

📝 Form Handling: Dedicated vs General-Purpose

formik exists solely for forms. It tracks values, errors, touched fields, and submission state automatically.

// Formik
import { useFormik } from 'formik';

function MyForm() {
  const formik = useFormik({
    initialValues: { email: '' },
    validate: (values) => {
      const errors = {};
      if (!values.email) errors.email = 'Required';
      return errors;
    },
    onSubmit: (values) => alert(JSON.stringify(values)),
  });

  return (
    <form onSubmit={formik.handleSubmit}>
      <input
        name="email"
        onChange={formik.handleChange}
        value={formik.values.email}
      />
      {formik.errors.email && <div>{formik.errors.email}</div>}
      <button type="submit">Submit</button>
    </form>
  );
}

Other libraries like zustand or redux can store form data, but they don’t handle validation, dirty checks, or submission orchestration. For anything beyond trivial forms, formik (or alternatives like react-hook-form) saves significant effort.

🌐 Server State vs Client State

react-query treats server data as a first-class citizen. It caches responses, deduplicates requests, and manages background updates.

// React Query
import { useQuery, useMutation } from '@tanstack/react-query';

function UserProfile({ userId }) {
  const { data, isLoading } = useQuery({
    queryKey: ['user', userId],
    queryFn: () => fetchUser(userId),
  });

  const mutation = useMutation({
    mutationFn: updateUser,
    onSuccess: () => {
      // Invalidate and refetch user data
      queryClient.invalidateQueries({ queryKey: ['user', userId] });
    },
  });

  if (isLoading) return <div>Loading...</div>;
  return <div>{data.name}</div>;
}

None of the other libraries (jotai, mobx, etc.) handle HTTP caching, retries, or stale-while-revalidate strategies. They’re for client state only. Always pair react-query (or similar) with a client-state library — they solve complementary problems.

🧠 Mental Models: Mutable vs Immutable vs Declarative

Mutable with Automatic Tracking (mobx)

MobX lets you write mutable code that “just works” thanks to proxies and observables.

// MobX
import { makeAutoObservable } from 'mobx';

class Timer {
  secondsPassed = 0;

  constructor() {
    makeAutoObservable(this);
  }

  increase() {
    this.secondsPassed += 1;
  }
}

const timer = new Timer();

// In component
import { observer } from 'mobx-react-lite';

const TimerView = observer(() => <div>{timer.secondsPassed}</div>);

Changes to secondsPassed automatically re-render TimerView. No reducers, no dispatches.

Immutable with Actions (redux, zustand)

Both enforce immutability but differ in API surface.

// Redux (with Redux Toolkit)
import { createSlice } from '@reduxjs/toolkit';

const counterSlice = createSlice({
  name: 'counter',
  initialState: { value: 0 },
  reducers: {
    increment: (state) => {
      state.value += 1; // Draft state is mutable
    },
  },
});

// In component
import { useSelector, useDispatch } from 'react-redux';

function Counter() {
  const count = useSelector((state) => state.counter.value);
  const dispatch = useDispatch();
  return <button onClick={() => dispatch(increment())}>{count}</button>;
}

// Zustand
import { create } from 'zustand';

const useStore = create((set) => ({
  count: 0,
  increment: () => set((state) => ({ count: state.count + 1 })),
}));

function Counter() {
  const { count, increment } = useStore();
  return <button onClick={increment}>{count}</button>;
}

Zustand skips providers and connects directly to components. Redux offers stronger devtooling and middleware.

Atomic and Derived (jotai, recoil)

Both use atoms (units of state) and selectors (derived state).

// Jotai
import { atom, useAtom } from 'jotai';

const countAtom = atom(0);
const doubleCountAtom = atom((get) => get(countAtom) * 2);

function Counter() {
  const [count, setCount] = useAtom(countAtom);
  const doubleCount = useAtomValue(doubleCountAtom);
  return <div>{doubleCount}</div>;
}

// Recoil
import { atom, selector, useRecoilState, useRecoilValue } from 'recoil';

const countState = atom({ key: 'count', default: 0 });
const doubleCountState = selector({
  key: 'doubleCount',
  get: ({ get }) => get(countState) * 2,
});

function Counter() {
  const [count, setCount] = useRecoilState(countState);
  const doubleCount = useRecoilValue(doubleCountState);
  return <div>{doubleCount}</div>;
}

Jotai doesn’t require string keys, avoids provider trees, and has a smaller API. Recoil’s string keys enable devtools but add verbosity.

🤖 State Machines for Complex Flows (xstate)

When logic has clear states and transitions (e.g., idle → loading → success/error), XState prevents invalid states.

// XState
import { createMachine, interpret } from 'xstate';

const fetchMachine = createMachine({
  id: 'fetch',
  initial: 'idle',
  states: {
    idle: { on: { FETCH: 'loading' } },
    loading: {
      on: { RESOLVE: 'success', REJECT: 'failure' },
    },
    success: { type: 'final' },
    failure: { on: { RETRY: 'loading' } },
  },
});

const service = interpret(fetchMachine).start();

// In component
import { useMachine } from '@xstate/react';

function FetchButton() {
  const [state, send] = useMachine(fetchMachine);

  if (state.matches('idle')) {
    return <button onClick={() => send('FETCH')}>Fetch</button>;
  }
  if (state.matches('loading')) return <div>Loading...</div>;
  if (state.matches('success')) return <div>Success!</div>;
  return <button onClick={() => send('RETRY')}>Retry</button>;
}

This guarantees you can’t show a “Retry” button in the “idle” state — impossible with boolean flags.

⚡ Performance Characteristics

  • Context-based solutions (not listed here, but relevant) cause re-renders for all consumers when any part of the context changes. zustand, jotai, and recoil avoid this by letting components subscribe to specific state slices.
  • mobx uses fine-grained reactivity: only components using a changed observable re-render.
  • redux requires useSelector with proper memoization (or RTK’s auto-memoized selectors) to prevent unnecessary renders.
  • react-query’s caching means components sharing the same query key automatically stay in sync without extra wiring.

🔌 Ecosystem and Extensibility

  • redux has the richest middleware ecosystem (thunks, sagas, observables) and devtools for time-travel debugging.
  • zustand supports middleware for persistence, logging, and immutability checks via simple function composition.
  • mobx integrates with React DevTools and offers utilities for serializing state.
  • react-query includes built-in support for pagination, infinite queries, and mutations with rollback.

🛑 Maintenance Status Notes

As of 2024:

  • recoil is in maintenance mode per Meta’s official statement. New projects should evaluate jotai as a more actively developed alternative with similar concepts.
  • All other libraries (formik, jotai, mobx, react-query, redux, xstate, zustand) are actively maintained with regular releases.

🔄 When to Combine Libraries

It’s common — and encouraged — to use multiple libraries together:

  • react-query + zustand: Use React Query for server data, Zustand for UI state (e.g., sidebar open/closed).
  • xstate + mobx: Use XState for workflow logic, MobX for the underlying data models.
  • formik + redux: Formik handles form state, Redux stores the final submitted data globally.

Avoid using two general-purpose state managers (e.g., Redux + Zustand) unless you have a very specific reason — it adds complexity without benefit.

📊 Summary Table

LibraryBest ForState ModelLearning CurveKey Strength
formikComplex formsForm-specificLowValidation, submission handling
jotaiGlobal/client stateAtomicLowMinimal, no providers, async atoms
mobxObject-oriented stateObservableMediumTransparent reactivity
react-queryServer dataCache-centricLowAutomatic caching, background updates
recoilFine-grained reactivityAtomicMediumSelectors, concurrent mode ready
reduxLarge-scale appsCentralizedMedium-HighDevtools, middleware, ecosystem
xstateStateful workflowsState machineHighPrevents invalid states
zustandSimple global stateHook-basedLowLightweight, no boilerplate

💡 Final Guidance

  • Start with react-query for any data from APIs — it’s transformative for async logic.
  • For client state, pick based on team preference:
    • Like Redux’s discipline? Use modern Redux Toolkit.
    • Prefer simplicity? Go with zustand.
    • Need fine-grained updates? Choose jotai (or mobx if you like mutability).
  • Use xstate only when your logic has clear states/transitions — don’t force it.
  • Reserve formik for forms too complex for basic useState.
  • Avoid recoil for new projects due to reduced maintenance; jotai is a drop-in conceptual replacement.

The right tool depends on your problem’s shape — not hype. Match the library to the task, and don’t hesitate to combine them when needed.

How to Choose: zustand vs formik vs jotai vs mobx vs react-query vs recoil vs redux vs xstate

  • zustand:

    Choose zustand for a lightweight, hook-based global state solution that avoids common pitfalls like context re-renders. It’s ideal for most medium-sized apps needing shared state without Redux’s ceremony, offering direct store access, middleware support, and easy persistence. Its simplicity and performance make it a strong default choice for client state when you don’t need fine-grained reactivity or state machine semantics.

  • formik:

    Choose formik when you need a battle-tested, dedicated solution for managing complex forms with validation, submission handling, and field-level state. It’s ideal for large forms with nested structures, dynamic fields, or intricate validation logic, especially when you want to avoid manually wiring up onChange handlers and error states. However, for simple forms or when using modern React patterns like controlled components with hooks, lighter alternatives may suffice.

  • jotai:

    Choose jotai when you want a minimal, atomic state model that scales from simple local state to complex global state without boilerplate. Its atoms compose naturally, support async and derived values out of the box, and integrate seamlessly with React’s concurrent features. It’s particularly well-suited for teams that prefer a functional, immutable approach but want better performance than context-based solutions through automatic render optimization.

  • mobx:

    Choose mobx when you prefer an object-oriented, mutable state model with transparent reactivity. It excels in scenarios where you have deeply nested or frequently updated state and want automatic dependency tracking without manual selectors or memoization. Use it if your team is comfortable with classes and decorators (though modern MobX supports plain objects) and values writing code that closely mirrors how data is used in views.

  • react-query:

    Choose react-query whenever your app fetches data from APIs. It handles caching, background refetching, mutations, pagination, and optimistic updates automatically, reducing the need for manual loading/error states and cache invalidation logic. It’s not a general-purpose state manager — pair it with another library like zustand or redux for client-only state, but let it manage all server-derived data.

  • recoil:

    Choose recoil if you want fine-grained reactivity with a declarative, atom-and-selector model that integrates tightly with React’s rendering lifecycle. It’s powerful for complex UIs where many components depend on overlapping subsets of state, as it minimizes unnecessary re-renders. However, note that Facebook has deprioritized its development; while stable, new projects might consider alternatives like jotai with similar ergonomics and active maintenance.

  • redux:

    Choose redux when you need a predictable, centralized store with strong devtooling, middleware support (like Redux Toolkit’s RTK Query), and a mature ecosystem. Modern Redux with Redux Toolkit eliminates much of the historical boilerplate and is well-suited for large applications requiring strict state traceability, time-travel debugging, or complex side-effect handling via middleware. Avoid it for small apps where its structure adds unnecessary overhead.

  • xstate:

    Choose xstate when your UI or business logic is best modeled as a finite state machine or statechart — for example, multi-step wizards, complex animations, or workflows with clear transitions between states. It enforces explicit state definitions and prevents invalid transitions, making logic easier to test and visualize. Pair it with other state libraries for data storage, as it focuses on control flow rather than data persistence.

Similar Npm Packages to zustand

zustand is a small, fast, and scalable state management library for React applications. It provides a simple API that allows developers to create global state stores with minimal boilerplate. Zustand's design focuses on performance and ease of use, making it an excellent choice for both small and large applications. It leverages React's hooks to manage state, allowing components to subscribe to specific slices of state without unnecessary re-renders.

While Zustand is a powerful option for state management, there are several alternatives in the React ecosystem that cater to different needs:

  • jotai is a primitive and flexible state management library that allows you to manage state using atoms. It provides a simple API for creating and updating state, making it easy to build complex applications without the overhead of a larger state management solution. Jotai is particularly useful for applications that require fine-grained control over state updates and dependencies.

  • mobx is a reactive state management library that uses observables to manage state. It allows developers to create observable state and automatically re-renders components when the state changes. MobX is particularly well-suited for applications that require a reactive programming model and can handle complex state relationships with ease.

  • react-query is primarily a data-fetching library, but it also provides state management capabilities for server state. It simplifies the process of fetching, caching, and synchronizing server data in React applications. If your application relies heavily on server data, react-query is an excellent choice for managing that state efficiently.

  • recoil is a state management library that provides a more efficient way to manage global state in React applications. It uses atoms and selectors to manage state and derive new state from existing state. Recoil is particularly useful for applications with complex state dependencies and relationships.

  • redux is one of the most popular state management libraries in the React ecosystem. It follows a unidirectional data flow and uses a centralized store to manage application state. Redux is well-suited for large applications with complex state management needs, but it can introduce significant boilerplate code.

  • valtio is a proxy-based state management library that provides a simple API for managing state. It allows developers to create reactive state stores that automatically update components when the state changes. Valtio is lightweight and easy to use, making it a good choice for applications that require a straightforward state management solution.

  • xstate is a state management library that uses finite state machines and statecharts to manage complex state logic. It is particularly useful for applications with intricate state transitions and workflows. XState provides a robust way to model state and transitions, making it ideal for applications that require precise control over state changes.

To explore how Zustand compares with these alternatives, check out the comparison: Comparing jotai vs mobx vs react-query vs recoil vs redux vs valtio vs xstate vs zustand.

Similar Npm Packages to formik

formik is a popular library for managing forms in React applications. It simplifies form handling by providing a set of utilities that help with form state management, validation, and submission. Formik is particularly useful for complex forms that require validation and dynamic field management, making it a go-to choice for many React developers. However, there are several alternatives that also cater to form management in React. Here are a few noteworthy options:

  • formik-material-ui is a wrapper around Formik that integrates Material-UI components with Formik's form management capabilities. This library allows developers to easily create forms using Material-UI components while leveraging Formik's powerful features for state management and validation. If you are already using Material-UI in your project and want to streamline form handling, formik-material-ui is an excellent choice.

  • react-final-form is a lightweight alternative to Formik that focuses on performance and simplicity. It is based on the Final Form library and provides a flexible API for managing form state. React Final Form allows for easy integration with various UI libraries and is particularly suitable for applications that require high performance with minimal overhead. If you prefer a more functional approach to form management, react-final-form is worth considering.

  • react-hook-form is another popular library that leverages React hooks for form management. It offers a simple and performant way to handle forms with minimal re-renders, making it a great choice for applications where performance is critical. React Hook Form is easy to integrate with existing UI libraries and provides built-in validation support. If you are looking for a modern and efficient way to manage forms in React, react-hook-form is a strong contender.

  • react-jsonschema-form is a library that allows you to create forms based on JSON Schema. It automatically generates form fields based on the schema definition, making it a great option for applications that require dynamic form generation. If your project involves working with JSON data structures and you want to automate form creation, react-jsonschema-form is an excellent choice.

  • redux-form is a library that integrates form management with Redux, allowing you to manage form state in the Redux store. While it provides powerful capabilities for managing complex forms, it may introduce additional complexity due to its reliance on Redux. If your application is already using Redux and you want to manage form state alongside your global state, redux-form can be a suitable option.

To explore how these libraries compare, check out the following link: Comparing formik vs formik-material-ui vs react-final-form vs react-hook-form vs react-jsonschema-form vs redux-form.

Similar Npm Packages to jotai

jotai is a state management library for React applications that emphasizes simplicity and minimalism. It allows developers to manage state using atoms, which are units of state that can be read from and written to. Jotai's API is designed to be intuitive, making it easy to integrate into existing React applications. Its focus on atomic state management allows for fine-grained updates, leading to better performance and easier debugging.

While jotai is a powerful option, there are several alternatives in the React ecosystem that cater to different state management needs:

  • mobx is a reactive state management library that allows developers to manage application state in a more declarative manner. It uses observable state and automatically tracks dependencies, making it easy to create responsive UIs. MobX is particularly well-suited for applications with complex state interactions and is known for its simplicity and performance.

  • react-query is a library designed for managing server state in React applications. It simplifies data fetching, caching, and synchronization, allowing developers to focus on building their applications without worrying about the complexities of data management. React Query is ideal for applications that rely heavily on remote data and require features like background updates and caching.

  • recoil provides a flexible state management solution that works seamlessly with React's concurrent features. It allows developers to manage both local and global state using atoms and selectors, making it a great choice for applications with complex state dependencies. Recoil is particularly useful for medium to large-scale applications that require a scalable state management solution.

  • redux is one of the most popular state management libraries in the React ecosystem. It follows a unidirectional data flow and uses a centralized store to manage application state. Redux is well-suited for large applications with complex state management needs, but it can introduce boilerplate code and complexity.

  • valtio is a proxy-based state management library that allows developers to manage state in a more straightforward and less verbose manner. It provides a simple API and enables automatic reactivity without the need for additional boilerplate code. Valtio is a good choice for developers looking for a lightweight and easy-to-use state management solution.

  • xstate is a state management library based on finite state machines and statecharts. It provides a powerful way to model complex state transitions and side effects, making it ideal for applications with intricate workflows. XState is particularly useful for applications that require clear state management and predictable behavior.

  • zustand is a minimalistic state management library that focuses on simplicity and performance. It provides a straightforward API for managing state without the overhead of additional boilerplate. Zustand is suitable for small to medium-sized applications where ease of use and speed of development are priorities.

To explore how jotai compares with these alternatives, check out the comparison: Comparing jotai vs mobx vs react-query vs recoil vs redux vs valtio vs xstate vs zustand.

Similar Npm Packages to mobx

mobx is a powerful state management library for JavaScript applications, particularly popular in the React ecosystem. It enables developers to manage application state in a reactive manner, allowing for automatic updates to the UI when the underlying state changes. MobX uses observable state and reactions, making it easy to create complex applications with minimal boilerplate code. Its simplicity and performance make it a great choice for applications that require a responsive and dynamic user interface. However, there are several alternatives to MobX that also provide effective state management solutions:

  • immer is a library that allows developers to work with immutable state in a more convenient way. It enables you to write code that appears to mutate state directly, while it actually produces a new immutable state. This can simplify state management, especially in applications where immutability is crucial. Immer is often used in conjunction with other state management libraries, including Redux, to streamline the process of updating state.

  • react-query is a powerful data-fetching library that focuses on managing server state. It simplifies the process of fetching, caching, and synchronizing data from APIs, making it an excellent choice for applications that rely heavily on remote data. React Query provides features like automatic caching, background updates, and query invalidation, which can significantly enhance the user experience when dealing with asynchronous data.

  • recoil is a state management library specifically designed for React applications. It introduces the concept of atoms and selectors to manage state in a more granular way, allowing for better performance and scalability. Recoil is particularly useful for applications with complex state dependencies, as it enables fine-grained control over state updates and reactivity.

  • redux is one of the most popular state management libraries in the React ecosystem. It follows a unidirectional data flow and uses a central store to manage application state. Redux is known for its predictable state management and middleware capabilities, making it suitable for large-scale applications. However, it can introduce boilerplate code and complexity, which some developers may want to avoid.

  • valtio is a minimalistic state management library that leverages JavaScript proxies to create a reactive state. It allows developers to manage state in a straightforward manner without the need for complex boilerplate code. Valtio is particularly appealing for those who prefer a simpler approach to state management while still benefiting from reactivity.

  • xstate is a state management library that uses finite state machines and statecharts to manage state in a predictable way. It is particularly useful for applications with complex state transitions and workflows. XState allows developers to visualize state transitions and manage side effects, making it a powerful tool for building robust applications.

  • zustand is a lightweight state management library that focuses on simplicity and performance. It provides a minimal API for managing state in React applications, making it easy to integrate into existing projects. Zustand is ideal for small to medium-sized applications where developers want a straightforward solution without the overhead of more complex libraries.

To see how MobX compares with these alternatives, check out the comparison: Comparing immer vs mobx vs react-query vs recoil vs redux vs valtio vs xstate vs zustand.

Similar Npm Packages to react-query

react-query is a powerful data-fetching and state management library for React applications. It simplifies the process of fetching, caching, and synchronizing server state, allowing developers to focus on building their applications without worrying about the complexities of data management. With features like automatic caching, background updates, and query invalidation, react-query is well-suited for applications that rely heavily on server data. It provides a robust solution for managing asynchronous data and is particularly useful in scenarios where data needs to be fetched frequently or updated in real-time.

While react-query is a fantastic choice for data fetching, there are several alternatives worth considering:

  • axios is a popular promise-based HTTP client for making requests to external APIs. While it is not a state management library itself, it is often used in conjunction with state management solutions to handle data fetching. Developers appreciate axios for its simplicity, ease of use, and ability to intercept requests and responses. If you prefer a straightforward approach to making HTTP requests without the additional features of a data-fetching library, axios is a solid choice.
  • redux-query is a library that integrates data fetching with Redux, allowing developers to manage server state alongside their application state. It provides a way to define queries and mutations in a Redux-friendly manner, making it easier to manage complex data-fetching scenarios. If your application already uses Redux for state management and you want to incorporate data fetching into that flow, redux-query can be a good fit.
  • swr is another data-fetching library for React that focuses on simplicity and performance. It provides features such as caching, revalidation, and automatic retries, similar to react-query. swr is designed to work seamlessly with React's hooks, making it a great option for developers looking for a minimalistic approach to data fetching. If you prefer a lightweight library that still offers powerful data-fetching capabilities, swr is worth considering.

To see how react-query compares with axios, redux-query, and swr, check out the comparison: Comparing axios vs react-query vs redux-query vs swr.

Similar Npm Packages to recoil

recoil is a state management library for React applications that provides a more flexible and efficient way to manage state compared to traditional solutions. It allows developers to create shared state that can be easily accessed and updated across components, making it particularly useful for applications with complex state dependencies. Recoil introduces concepts like Atoms and Selectors, which help manage both local and global state in a more intuitive way.

While Recoil is a powerful tool for state management, there are several alternatives that cater to different needs and preferences:

  • formik is a popular library for managing form state in React applications. It simplifies the process of handling form inputs, validation, and submission. While Formik is specifically designed for forms, it can be a great choice if your application heavily relies on form handling and you want to manage form state efficiently.

  • jotai is a state management library that focuses on simplicity and atomic state management. It allows developers to create and manage state using atoms, which are units of state that can be shared across components. Jotai is particularly useful for applications that require a minimalistic approach to state management without the complexity of larger libraries.

  • mobx is a state management library that uses observable state and reactive programming principles. It allows developers to create observable data structures that automatically update the UI when the state changes. MobX is a great choice for applications that require fine-grained reactivity and a more object-oriented approach to state management.

  • react-query is a powerful library for managing server state in React applications. It provides features like caching, synchronization, and background updates, making it ideal for applications that rely heavily on data fetching from APIs. React Query excels in scenarios where managing server state is crucial, while Recoil focuses more on local state management.

  • redux is a widely-used state management library that follows a unidirectional data flow and uses a centralized store. Redux is great for large applications with complex state management needs, but it can introduce boilerplate code and complexity. Recoil offers a more flexible approach, allowing for easier state management without the need for reducers and actions.

  • xstate is a state management library that uses finite state machines and statecharts to manage application state. It is particularly useful for applications with complex state transitions and workflows. XState provides a visual representation of state transitions, making it easier to understand and manage application logic.

  • zustand is a minimalist state management library that focuses on simplicity and performance. It allows developers to create global state stores with a straightforward API. Zustand is ideal for small to medium-sized applications where a lightweight solution is preferred over more complex state management libraries.

To see how Recoil compares with these alternatives, check out the comparison: Comparing formik vs jotai vs mobx vs react-query vs recoil vs redux vs xstate vs zustand.

Similar Npm Packages to redux

redux is a popular state management library for JavaScript applications, particularly those built with React. It provides a centralized store for application state, enabling predictable state updates through actions and reducers. Redux is known for its strict unidirectional data flow, making it easier to understand and debug applications. However, there are several alternatives available that cater to different needs and preferences. Here are some notable alternatives:

  • effector is a fast and powerful state management library that emphasizes a functional approach to state management. It allows developers to create reactive state stores and manage side effects with ease. Effector's unique model enables fine-grained control over state changes and dependencies, making it suitable for complex applications where performance is critical. If you prefer a more functional and reactive programming style, effector is a great choice.

  • mobx is another state management library that focuses on simplicity and reactivity. It uses observable state and allows for automatic updates of components when the state changes. MobX is particularly well-suited for applications that require a more intuitive and less boilerplate-heavy approach to state management. If you want to manage state with minimal configuration and enjoy a reactive programming model, MobX is worth considering.

  • react-query is a powerful library for managing server state in React applications. While it is not a direct replacement for Redux, it complements it by providing tools for fetching, caching, and synchronizing server data. React Query simplifies data fetching and state management, making it ideal for applications that rely heavily on API interactions. If your application requires efficient data fetching and caching, React Query is an excellent addition.

  • recoil is a state management library developed by Facebook that provides a more flexible and scalable approach to managing state in React applications. It allows for fine-grained control over state and supports derived state and asynchronous queries. Recoil is a great choice for applications with complex state dependencies and relationships, offering a more modern alternative to Redux.

  • redux-saga is a middleware library for Redux that helps manage side effects in a more manageable way. It allows developers to write complex asynchronous logic using generator functions, making it easier to handle complex workflows. If your application requires sophisticated side effect management, redux-saga can enhance your Redux setup.

  • redux-thunk is another middleware for Redux that simplifies handling asynchronous actions. It allows you to write action creators that return a function instead of an action, enabling you to perform asynchronous operations before dispatching actions. If you need a straightforward way to handle asynchronous logic in Redux, redux-thunk is a popular choice.

  • xstate is a state management library that uses finite state machines and statecharts to model application state. It provides a powerful way to manage complex state transitions and side effects, making it suitable for applications with intricate state logic. If you prefer a more formal approach to state management with clear state transitions, XState is a compelling option.

  • zustand is a minimalist state management library that focuses on simplicity and performance. It provides a straightforward API for managing state in React applications without the boilerplate associated with Redux. If you are looking for a lightweight and easy-to-use alternative for state management, Zustand is a great choice.

To explore how these libraries compare, check out the comparison: Comparing effector vs mobx vs react-query vs recoil vs redux vs redux-saga vs redux-thunk vs xstate vs zustand.

Similar Npm Packages to xstate

xstate is a state management library that utilizes finite state machines and statecharts to manage complex state logic in applications. It provides a robust framework for modeling state transitions and handling side effects, making it particularly useful for applications with intricate state management needs. While xstate offers a powerful approach to managing state, there are several alternatives in the ecosystem that cater to different use cases:

  • effector is a fast and powerful state management library that focuses on reactive programming. It allows developers to create complex applications with a simple and intuitive API. Effector is designed to be highly efficient, enabling fine-grained reactivity and easy composition of state and effects. If you are looking for a library that emphasizes performance and a functional approach to state management, effector is an excellent choice.

  • mobx is a simple and scalable state management library that uses observable data structures to automatically track dependencies and update the UI when the state changes. MobX is particularly well-suited for applications where you want to minimize boilerplate code and focus on reactive programming. Its straightforward API and powerful reactivity model make it a popular choice for many developers.

  • react-query is a library designed for managing server state in React applications. It simplifies data fetching, caching, and synchronization, making it easier to work with remote data. While react-query primarily focuses on server state, it can be used alongside other state management libraries to handle client state. If your application relies heavily on remote data and requires efficient data-fetching capabilities, react-query is a great option.

  • recoil is a state management library that provides a more efficient and scalable way to manage complex state in React applications. It introduces concepts like atoms and selectors to manage state dependencies and derived state. Recoil is particularly useful for applications with intricate state relationships and can be a good alternative to more traditional state management solutions.

  • redux is one of the most popular state management libraries in the React ecosystem. It follows a unidirectional data flow and uses a centralized store to manage application state. Redux is well-suited for large applications with complex state management needs, but it can introduce boilerplate code. If you are building a large-scale application and need a robust solution, Redux is a tried-and-true option.

  • vuex is a state management library specifically designed for Vue.js applications. It follows a similar pattern to Redux but is tailored for the Vue ecosystem. If you are working with Vue.js and need a centralized state management solution, Vuex is the go-to library.

  • zustand is a minimalist state management library that focuses on simplicity and performance. It provides a straightforward API for managing state without the complexity of more extensive libraries. Zustand is ideal for small to medium-sized projects where you want to maintain a lightweight approach to state management.

To see how xstate compares with effector, mobx, react-query, recoil, redux, vuex, and zustand, check out the comparison: Comparing effector vs mobx vs react-query vs recoil vs redux vs vuex vs xstate vs zustand.

README for zustand

Build Status Build Size Version Downloads Discord Shield

A small, fast and scalable bearbones state-management solution using simplified flux principles. Has a comfy API based on hooks, isn't boilerplatey or opinionated.

Don't disregard it because it's cute. It has quite the claws, lots of time was spent dealing with common pitfalls, like the dreaded zombie child problem, react concurrency, and context loss between mixed renderers. It may be the one state-manager in the React space that gets all of these right.

You can try a live demo and read the docs.

npm install zustand

:warning: This readme is written for JavaScript users. If you are a TypeScript user, be sure to check out our TypeScript Usage section.

First create a store

Your store is a hook! You can put anything in it: primitives, objects, functions. State has to be updated immutably and the set function merges state to help it.

import { create } from 'zustand'

const useBearStore = create((set) => ({
  bears: 0,
  increasePopulation: () => set((state) => ({ bears: state.bears + 1 })),
  removeAllBears: () => set({ bears: 0 }),
}))

Then bind your components, and that's it!

Use the hook anywhere, no providers are needed. Select your state and the component will re-render on changes.

function BearCounter() {
  const bears = useBearStore((state) => state.bears)
  return <h1>{bears} around here ...</h1>
}

function Controls() {
  const increasePopulation = useBearStore((state) => state.increasePopulation)
  return <button onClick={increasePopulation}>one up</button>
}

Why zustand over redux?

Why zustand over context?

  • Less boilerplate
  • Renders components only on changes
  • Centralized, action-based state management

Recipes

Fetching everything

You can, but bear in mind that it will cause the component to update on every state change!

const state = useBearStore()

Selecting multiple state slices

It detects changes with strict-equality (old === new) by default, this is efficient for atomic state picks.

const nuts = useBearStore((state) => state.nuts)
const honey = useBearStore((state) => state.honey)

If you want to construct a single object with multiple state-picks inside, similar to redux's mapStateToProps, you can use useShallow to prevent unnecessary rerenders when the selector output does not change according to shallow equal.

import { create } from 'zustand'
import { useShallow } from 'zustand/react/shallow'

const useBearStore = create((set) => ({
  nuts: 0,
  honey: 0,
  treats: {},
  // ...
}))

// Object pick, re-renders the component when either state.nuts or state.honey change
const { nuts, honey } = useBearStore(
  useShallow((state) => ({ nuts: state.nuts, honey: state.honey })),
)

// Array pick, re-renders the component when either state.nuts or state.honey change
const [nuts, honey] = useBearStore(
  useShallow((state) => [state.nuts, state.honey]),
)

// Mapped picks, re-renders the component when state.treats changes in order, count or keys
const treats = useBearStore(useShallow((state) => Object.keys(state.treats)))

For more control over re-rendering, you may provide any custom equality function (this example requires the use of createWithEqualityFn).

const treats = useBearStore(
  (state) => state.treats,
  (oldTreats, newTreats) => compare(oldTreats, newTreats),
)

Overwriting state

The set function has a second argument, false by default. Instead of merging, it will replace the state model. Be careful not to wipe out parts you rely on, like actions.

const useFishStore = create((set) => ({
  salmon: 1,
  tuna: 2,
  deleteEverything: () => set({}, true), // clears the entire store, actions included
  deleteTuna: () => set(({ tuna, ...rest }) => rest, true),
}))

Async actions

Just call set when you're ready, zustand doesn't care if your actions are async or not.

const useFishStore = create((set) => ({
  fishies: {},
  fetch: async (pond) => {
    const response = await fetch(pond)
    set({ fishies: await response.json() })
  },
}))

Read from state in actions

set allows fn-updates set(state => result), but you still have access to state outside of it through get.

const useSoundStore = create((set, get) => ({
  sound: 'grunt',
  action: () => {
    const sound = get().sound
    ...

Reading/writing state and reacting to changes outside of components

Sometimes you need to access state in a non-reactive way or act upon the store. For these cases, the resulting hook has utility functions attached to its prototype.

:warning: This technique is not recommended for adding state in React Server Components (typically in Next.js 13 and above). It can lead to unexpected bugs and privacy issues for your users. For more details, see #2200.

const useDogStore = create(() => ({ paw: true, snout: true, fur: true }))

// Getting non-reactive fresh state
const paw = useDogStore.getState().paw
// Listening to all changes, fires synchronously on every change
const unsub1 = useDogStore.subscribe(console.log)
// Updating state, will trigger listeners
useDogStore.setState({ paw: false })
// Unsubscribe listeners
unsub1()

// You can of course use the hook as you always would
function Component() {
  const paw = useDogStore((state) => state.paw)
  ...

Using subscribe with selector

If you need to subscribe with a selector, subscribeWithSelector middleware will help.

With this middleware subscribe accepts an additional signature:

subscribe(selector, callback, options?: { equalityFn, fireImmediately }): Unsubscribe

import { subscribeWithSelector } from 'zustand/middleware'
const useDogStore = create(
  subscribeWithSelector(() => ({ paw: true, snout: true, fur: true })),
)

// Listening to selected changes, in this case when "paw" changes
const unsub2 = useDogStore.subscribe((state) => state.paw, console.log)
// Subscribe also exposes the previous value
const unsub3 = useDogStore.subscribe(
  (state) => state.paw,
  (paw, previousPaw) => console.log(paw, previousPaw),
)
// Subscribe also supports an optional equality function
const unsub4 = useDogStore.subscribe(
  (state) => [state.paw, state.fur],
  console.log,
  { equalityFn: shallow },
)
// Subscribe and fire immediately
const unsub5 = useDogStore.subscribe((state) => state.paw, console.log, {
  fireImmediately: true,
})

Using zustand without React

Zustand core can be imported and used without the React dependency. The only difference is that the create function does not return a hook, but the API utilities.

import { createStore } from 'zustand/vanilla'

const store = createStore((set) => ...)
const { getState, setState, subscribe, getInitialState } = store

export default store

You can use a vanilla store with useStore hook available since v4.

import { useStore } from 'zustand'
import { vanillaStore } from './vanillaStore'

const useBoundStore = (selector) => useStore(vanillaStore, selector)

:warning: Note that middlewares that modify set or get are not applied to getState and setState.

Transient updates (for often occurring state-changes)

The subscribe function allows components to bind to a state-portion without forcing re-render on changes. Best combine it with useEffect for automatic unsubscribe on unmount. This can make a drastic performance impact when you are allowed to mutate the view directly.

const useScratchStore = create((set) => ({ scratches: 0, ... }))

const Component = () => {
  // Fetch initial state
  const scratchRef = useRef(useScratchStore.getState().scratches)
  // Connect to the store on mount, disconnect on unmount, catch state-changes in a reference
  useEffect(() => useScratchStore.subscribe(
    state => (scratchRef.current = state.scratches)
  ), [])
  ...

Sick of reducers and changing nested states? Use Immer!

Reducing nested structures is tiresome. Have you tried immer?

import { produce } from 'immer'

const useLushStore = create((set) => ({
  lush: { forest: { contains: { a: 'bear' } } },
  clearForest: () =>
    set(
      produce((state) => {
        state.lush.forest.contains = null
      }),
    ),
}))

const clearForest = useLushStore((state) => state.clearForest)
clearForest()

Alternatively, there are some other solutions.

Persist middleware

You can persist your store's data using any kind of storage.

import { create } from 'zustand'
import { persist, createJSONStorage } from 'zustand/middleware'

const useFishStore = create(
  persist(
    (set, get) => ({
      fishes: 0,
      addAFish: () => set({ fishes: get().fishes + 1 }),
    }),
    {
      name: 'food-storage', // name of the item in the storage (must be unique)
      storage: createJSONStorage(() => sessionStorage), // (optional) by default, 'localStorage' is used
    },
  ),
)

See the full documentation for this middleware.

Immer middleware

Immer is available as middleware too.

import { create } from 'zustand'
import { immer } from 'zustand/middleware/immer'

const useBeeStore = create(
  immer((set) => ({
    bees: 0,
    addBees: (by) =>
      set((state) => {
        state.bees += by
      }),
  })),
)

Can't live without redux-like reducers and action types?

const types = { increase: 'INCREASE', decrease: 'DECREASE' }

const reducer = (state, { type, by = 1 }) => {
  switch (type) {
    case types.increase:
      return { grumpiness: state.grumpiness + by }
    case types.decrease:
      return { grumpiness: state.grumpiness - by }
  }
}

const useGrumpyStore = create((set) => ({
  grumpiness: 0,
  dispatch: (args) => set((state) => reducer(state, args)),
}))

const dispatch = useGrumpyStore((state) => state.dispatch)
dispatch({ type: types.increase, by: 2 })

Or, just use our redux-middleware. It wires up your main-reducer, sets the initial state, and adds a dispatch function to the state itself and the vanilla API.

import { redux } from 'zustand/middleware'

const useGrumpyStore = create(redux(reducer, initialState))

Redux devtools

Install the Redux DevTools Chrome extension to use the devtools middleware.

import { devtools } from 'zustand/middleware'

// Usage with a plain action store, it will log actions as "setState"
const usePlainStore = create(devtools((set) => ...))
// Usage with a redux store, it will log full action types
const useReduxStore = create(devtools(redux(reducer, initialState)))

One redux devtools connection for multiple stores

import { devtools } from 'zustand/middleware'

// Usage with a plain action store, it will log actions as "setState"
const usePlainStore1 = create(devtools((set) => ..., { name, store: storeName1 }))
const usePlainStore2 = create(devtools((set) => ..., { name, store: storeName2 }))
// Usage with a redux store, it will log full action types
const useReduxStore1 = create(devtools(redux(reducer, initialState)), { name, store: storeName3 })
const useReduxStore2 = create(devtools(redux(reducer, initialState)), { name, store: storeName4 })

Assigning different connection names will separate stores in redux devtools. This also helps group different stores into separate redux devtools connections.

devtools takes the store function as its first argument, optionally you can name the store or configure serialize options with a second argument.

Name store: devtools(..., {name: "MyStore"}), which will create a separate instance named "MyStore" in the devtools.

Serialize options: devtools(..., { serialize: { options: true } }).

Logging Actions

devtools will only log actions from each separated store unlike in a typical combined reducers redux store. See an approach to combining stores https://github.com/pmndrs/zustand/issues/163

You can log a specific action type for each set function by passing a third parameter:

const useBearStore = create(devtools((set) => ({
  ...
  eatFish: () => set(
    (prev) => ({ fishes: prev.fishes > 1 ? prev.fishes - 1 : 0 }),
    undefined,
    'bear/eatFish'
  ),
  ...

You can also log the action's type along with its payload:

  ...
  addFishes: (count) => set(
    (prev) => ({ fishes: prev.fishes + count }),
    undefined,
    { type: 'bear/addFishes', count, }
  ),
  ...

If an action type is not provided, it is defaulted to "anonymous". You can customize this default value by providing an anonymousActionType parameter:

devtools(..., { anonymousActionType: 'unknown', ... })

If you wish to disable devtools (on production for instance). You can customize this setting by providing the enabled parameter:

devtools(..., { enabled: false, ... })

React context

The store created with create doesn't require context providers. In some cases, you may want to use contexts for dependency injection or if you want to initialize your store with props from a component. Because the normal store is a hook, passing it as a normal context value may violate the rules of hooks.

The recommended method available since v4 is to use the vanilla store.

import { createContext, useContext } from 'react'
import { createStore, useStore } from 'zustand'

const store = createStore(...) // vanilla store without hooks

const StoreContext = createContext()

const App = () => (
  <StoreContext.Provider value={store}>
    ...
  </StoreContext.Provider>
)

const Component = () => {
  const store = useContext(StoreContext)
  const slice = useStore(store, selector)
  ...

TypeScript Usage

Basic typescript usage doesn't require anything special except for writing create<State>()(...) instead of create(...)...

import { create } from 'zustand'
import { devtools, persist } from 'zustand/middleware'
import type {} from '@redux-devtools/extension' // required for devtools typing

interface BearState {
  bears: number
  increase: (by: number) => void
}

const useBearStore = create<BearState>()(
  devtools(
    persist(
      (set) => ({
        bears: 0,
        increase: (by) => set((state) => ({ bears: state.bears + by })),
      }),
      {
        name: 'bear-storage',
      },
    ),
  ),
)

A more detailed TypeScript guide is here and there.

Best practices

Third-Party Libraries

Some users may want to extend Zustand's feature set which can be done using third-party libraries made by the community. For information regarding third-party libraries with Zustand, visit the doc.

Comparison with other libraries

npm-compare.com is an independent website designed to help developers choose the most suitable npm packages. We are not affiliated with npm, Inc, the official website for the npm registry. Note that npm is a registered trademark of npm, Inc. Please share your feedback via our GitHub repository. For more details, please refer to our Terms & Privacy.