Async components

Search…
Async components
The most common use case for React Async is data fetching. In single-page applications it's very common to dynamically load some data from a backend. React Async makes it incredibly easy to set this up, without having to worry about the details.
The mental model of React Async is component-first. Rather than loading data high up in your application and passing it down to a component for display, you perform the data loading at the component level. Such a component is called an async component. An async component can render its state in a meaningful way like any other component, or be logic-only. In that case it doesn't render any UI but instead passes its state down to its children. Such separation of concerns is good practice.
Creating an async component with useFetch
The easiest way to create an async component for data fetching is through the useFetch hook:
1
import React from "react"
2
import { useFetch } from "react-async"
3
​
4
const Person = ({ id }) => {
5
  const { data, error } = useFetch(`https://swapi.co/api/people/${id}/`, {
6
    headers: { accept: "application/json" },
7
  })
8
  if (error) return error.message
9
  if (data) return `Hi, my name is ${data.name}!`
10
  return null
11
}
12
​
13
const App = () => {
14
  return <Person id={1} />
15
}
Copied!
More flexibility with useAsync
For most data fetching needs, useFetch is sufficient. However, sometimes you may want to take full control, for example if you want to combine multiple requests. In this case you can use the useAsync hook.
The core concept of useAsync (and React Async in general), is the promiseFn: a function that returns a Promise. It's the fundamental concept for modelling asynchronous operations. It enables React Async to take control over scheduling, the Promise lifecycle and things like (re)starting an operation on user action or other changes. We've deliberately chosen the Promise as our primitive, because it's natively supported and has various utility methods like Promise.all. That's also why you'll find our terminology closely follows the Promise states and fates.
The above example, written with useAsync, would look like this:
1
import React from "react"
2
import { useAsync } from "react-async"
3
​
4
const fetchPerson = async ({ id }, { signal }) => {
5
  const response = await fetch(`https://swapi.co/api/people/${id}/`, { signal })
6
  if (!response.ok) throw new Error(response.status)
7
  return response.json()
8
}
9
​
10
const Person = ({ id }) => {
11
  const { data, error } = useAsync({ promiseFn: fetchPerson, id })
12
  if (error) return error.message
13
  if (data) return `Hi, my name is ${data.name}!`
14
  return null
15
}
16
​
17
const App = () => {
18
  return <Person id={1} />
19
}
Copied!
Notice the incoming parameters to fetchPerson. The promiseFn will be invoked with a props object and an AbortController. props are the options you passed to useAsync, which is why you can access the id property using object destructuring. The AbortController is created by React Async to enable abortable fetch, so the underlying request will be aborted when the promise is cancelled (e.g. when a new one starts or we leave the page). We have to pass its AbortSignal down to fetch in order to wire this up.
API - Previous
Helper components
Next - Guide
Separating view and logic
Last modified 2yr ago
Copy link
Contents
Creating an async component with useFetch
More flexibility with useAsync
Creating an async component with `useFetch`

More flexibility with `useAsync`
