99 lines
6.9 KiB
Markdown
99 lines
6.9 KiB
Markdown
|
# Redux Toolkit
|
||
|
|
|
||
|
|
|
||
|
|
[](https://www.npmjs.com/package/@reduxjs/toolkit)
|
||
|
|
[](https://www.npmjs.com/package/@reduxjs/toolkit)
|
||
|
|
|
||
|
|
**The official, opinionated, batteries-included toolset for efficient Redux development**
|
||
|
|
|
||
|
|
(Formerly known as "Redux Starter Kit")
|
||
|
|
|
||
|
|
## Installation
|
||
|
|
|
||
|
|
### Using Create React App
|
||
|
|
|
||
|
|
The recommended way to start new apps with React and Redux Toolkit is by using the [official Redux+JS template](https://github.com/reduxjs/cra-template-redux) for [Create React App](https://github.com/facebook/create-react-app), which takes advantage of React Redux's integration with React components.
|
||
|
|
|
||
|
|
```sh
|
||
|
|
npx create-react-app my-app --template redux
|
||
|
|
```
|
||
|
|
|
||
|
|
Or if you are a TypeScript user, use [cra-template-redux-typescript](https://github.com/reduxjs/cra-template-redux-typescript), which is based on that template
|
||
|
|
|
||
|
|
```sh
|
||
|
|
npx create-react-app my-app --template redux-typescript
|
||
|
|
```
|
||
|
|
|
||
|
|
### An Existing App
|
||
|
|
|
||
|
|
Redux Toolkit is available as a package on NPM for use with a module bundler or in a Node application:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
# NPM
|
||
|
|
npm install @reduxjs/toolkit
|
||
|
|
|
||
|
|
# Yarn
|
||
|
|
yarn add @reduxjs/toolkit
|
||
|
|
```
|
||
|
|
|
||
|
|
It is also available as a precompiled UMD package that defines a `window.RTK` global variable.
|
||
|
|
The UMD package can be used as a [`<script>` tag](https://unpkg.com/@reduxjs/toolkit/dist/redux-toolkit.umd.js) directly.
|
||
|
|
|
||
|
|
## Purpose
|
||
|
|
|
||
|
|
The **Redux Toolkit** package is intended to be the standard way to write Redux logic. It was originally created to help address three common concerns about Redux:
|
||
|
|
|
||
|
|
- "Configuring a Redux store is too complicated"
|
||
|
|
- "I have to add a lot of packages to get Redux to do anything useful"
|
||
|
|
- "Redux requires too much boilerplate code"
|
||
|
|
|
||
|
|
We can't solve every use case, but in the spirit of [`create-react-app`](https://github.com/facebook/create-react-app), we can try to provide some tools that abstract over the setup process and handle the most common use cases, as well as include some useful utilities that will let the user simplify their application code.
|
||
|
|
|
||
|
|
Because of that, this package is deliberately limited in scope. It does _not_ address concepts like "reusable encapsulated Redux modules", folder or file structures, managing entity relationships in the store, and so on.
|
||
|
|
|
||
|
|
Redux Toolkit also includes a powerful data fetching and caching capability that we've dubbed "RTK Query". It's included in the package as a separate set of entry points. It's optional, but can eliminate the need to hand-write data fetching logic yourself.
|
||
|
|
|
||
|
|
## What's Included
|
||
|
|
|
||
|
|
Redux Toolkit includes these APIs:
|
||
|
|
|
||
|
|
- `configureStore()`: wraps `createStore` to provide simplified configuration options and good defaults. It can automatically combine your slice reducers, add whatever Redux middleware you supply, includes `redux-thunk` by default, and enables use of the Redux DevTools Extension.
|
||
|
|
- `createReducer()`: lets you supply a lookup table of action types to case reducer functions, rather than writing switch statements. In addition, it automatically uses the [`immer` library](https://github.com/mweststrate/immer) to let you write simpler immutable updates with normal mutative code, like `state.todos[3].completed = true`.
|
||
|
|
- `createAction()`: generates an action creator function for the given action type string. The function itself has `toString()` defined, so that it can be used in place of the type constant.
|
||
|
|
- `createSlice()`: combines `createReducer()` + `createAction()`. Accepts an object of reducer functions, a slice name, and an initial state value, and automatically generates a slice reducer with corresponding action creators and action types.
|
||
|
|
- `createListenerMiddleware()`: lets you define "listener" entries that contain an "effect" callback with additional logic, and a way to specify when that callback should run based on dispatched actions or state changes. A lightweight alternative to Redux async middleware like sagas and observables.
|
||
|
|
- `createAsyncThunk()`: accepts an action type string and a function that returns a promise, and generates a thunk that dispatches `pending/resolved/rejected` action types based on that promise
|
||
|
|
- `createEntityAdapter()`: generates a set of reusable reducers and selectors to manage normalized data in the store
|
||
|
|
- The `createSelector()` utility from the [Reselect](https://github.com/reduxjs/reselect) library, re-exported for ease of use.
|
||
|
|
|
||
|
|
## RTK Query
|
||
|
|
|
||
|
|
**RTK Query** is provided as an optional addon within the `@reduxjs/toolkit` package. It is purpose-built to solve the use case of data fetching and caching, supplying a compact, but powerful toolset to define an API interface layer for your app. It is intended to simplify common cases for loading data in a web application, eliminating the need to hand-write data fetching & caching logic yourself.
|
||
|
|
|
||
|
|
RTK Query is built on top of the Redux Toolkit core for its implementation, using [Redux](https://redux.js.org/) internally for its architecture. Although knowledge of Redux and RTK are not required to use RTK Query, you should explore all of the additional global store management capabilities they provide, as well as installing the [Redux DevTools browser extension](https://github.com/reduxjs/redux-devtools), which works flawlessly with RTK Query to traverse and replay a timeline of your request & cache behavior.
|
||
|
|
|
||
|
|
RTK Query is included within the installation of the core Redux Toolkit package. It is available via either of the two entry points below:
|
||
|
|
|
||
|
|
```ts no-transpile
|
||
|
|
import { createApi } from '@reduxjs/toolkit/query'
|
||
|
|
|
||
|
|
/* React-specific entry point that automatically generates
|
||
|
|
hooks corresponding to the defined endpoints */
|
||
|
|
import { createApi } from '@reduxjs/toolkit/query/react'
|
||
|
|
```
|
||
|
|
|
||
|
|
### What's included
|
||
|
|
|
||
|
|
RTK Query includes these APIs:
|
||
|
|
|
||
|
|
- `createApi()`: The core of RTK Query's functionality. It allows you to define a set of endpoints describe how to retrieve data from a series of endpoints, including configuration of how to fetch and transform that data. In most cases, you should use this once per app, with "one API slice per base URL" as a rule of thumb.
|
||
|
|
- `fetchBaseQuery()`: A small wrapper around fetch that aims to simplify requests. Intended as the recommended baseQuery to be used in createApi for the majority of users.
|
||
|
|
- `<ApiProvider />`: Can be used as a Provider if you do not already have a Redux store.
|
||
|
|
- `setupListeners()`: A utility used to enable refetchOnMount and refetchOnReconnect behaviors.
|
||
|
|
|
||
|
|
See the [**RTK Query Overview**](https://redux-toolkit.js.org/rtk-query/overview) page for more details on what RTK Query is, what problems it solves, and how to use it.
|
||
|
|
|
||
|
|
## Documentation
|
||
|
|
|
||
|
|
The Redux Toolkit docs are available at **https://redux-toolkit.js.org**.
|