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)
Part 1: React Hooks and Micro State Management
Part 2: Basic Approaches to the Global State
Part 3: Library Implementations and Their Uses

Understanding when to use Context

Before diving into learning the way to combine Context and Subscription, let's recap how Context works.

The following is a simple Context example with a theme. So, we specify a default value for createContext:

const ThemeContext = createContext("light");
const Component = () => {
  const theme = useContext(ThemeContext);
  return <div>Theme: {theme}</div>

What useContext(ThemeContext) returns depends on the Context in the component tree.

To change the Context value, we use a Provider component in Context as follows:

<ThemeContext.Provider value="dark">
  <Component />

In this case, Component will show the theme as dark.

The provider can be nested. It will use the value from the innermost provider:

<ThemeContext.Provider value="this value is not used">
  <ThemeContext.Provider value...