Book Image

Micro State Management with React Hooks

By : Daishi Kato
Book Image

Micro State Management with React Hooks

By: Daishi Kato

Overview of this book

State management is one of the most complex concepts in React. Traditionally, developers have used monolithic state management solutions. Thanks to React Hooks, micro state management is something tuned for moving your application from a monolith to a microservice. This book provides a hands-on approach to the implementation of micro state management that will have you up and running and productive in no time. You’ll learn basic patterns for state management in React and understand how to overcome the challenges encountered when you need to make the state global. Later chapters will show you how slicing a state into pieces is the way to overcome limitations. Using hooks, you'll see how you can easily reuse logic and have several solutions for specific domains, such as form state and server cache state. Finally, you'll explore how to use libraries such as Zustand, Jotai, and Valtio to organize state and manage development efficiently. By the end of this React book, you'll have learned how to choose the right global state management solution for your app requirement.
Table of Contents (16 chapters)
1
Part 1: React Hooks and Micro State Management
3
Part 2: Basic Approaches to the Global State
8
Part 3: Library Implementations and Their Uses

Exploring Valtio, another module state library

Valtio is a library primarily used for module state, which is the same as Zustand.

As we learned in Chapter 7, Use Case Scenario 1 – Zustand, we create a store in Zustand as follows:

const store = create(() => ({
  count: 0,
  text: "hello",
}));

The store variable has some properties, one of which is setState. With setState, we can update the state. For example, the following is incrementing the count value:

store.setState((prev) => ({
  count: prev.count + 1,
}))

Why do we need to use setState to update a state value? Because we want to update the state immutably. Internally, the previous setState works like the following:

moduleState = Object.assign({}, moduleState, {
  count: moduleState.count + 1
});

This is the way to update an object immutably.

Let's imagine a case where we don't need to follow the immutable update rule. In this case...