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

Best practices for using Context

In this section, we will learn three patterns to deal with Contexts for a global state, as follows:

  • Creating custom hooks and provider components
  • A factory pattern with a custom hook
  • Avoiding provider nesting with reduceRight

Let's take a look at each one.

Creating custom hooks and provider components

In the previous examples in this chapter, we directly used useContext to get Context values. Now, we will explicitly create custom hooks to access Context values as well as provider components. This allows us to hide Contexts and restrict their usage.

The following example creates custom hooks and provider components. We make a default Context value null and check if the value is null in the custom hooks. This checks if the custom hooks are used under the providers.

The first thing we do, as always, is to create a Context; this time, the default value of the Context is null, which indicates that the default value...