Hackernoon logoMagic of React Suspense with concurrent react and React.lazy API by@vivek-nayyar

Magic of React Suspense with concurrent react and React.lazy API

Vivek Nayyar Hacker Noon profile picture

@vivek-nayyarVivek Nayyar

👋 Senior Software Engineer with 5 years' of experience building products for numerous domains.

(Magical land of React Suspense, Concurrent React and React.lazy API)

Dan Abramov in his talk “Beyond React 16” at JSConf Iceland 2018 said:

We’ve built a generic way to ensure that high-priority updates like user input don’t get blocked by rendering low-priority updates.

Let’s understand what this means and also get introduced to some of the new features coming to React, some of which have been released as part of the latest stable release and some of them are still in unstable mode and it’s quite possible that the implementation of the api might change over time.

Things we got introduced to in the talk:


React.Suspense in simple words means we can suspend the rendering of our component or components until some condition is met( for example data from an endpoint or a resource is loaded) and until then show a fallback(for-example a spinner)

Why do we need this?

If suspense is all about just showing a spinner till data loads, can we not do that today as well?

I mean we have been doing the same thing since a long time by keeping a loading state as true and till the data is not fetched we show a spinner and when data fetch is complete we set the loading state to false.

An example of how we have been currently doing it:

state = {
  loading: true,
  data: null

So the question is if it can be done even today then what is it that suspense is bringing into our codebase?

The answer to that is yes it’s still possible to use loading state and play around with it to show/hide the spinner but as the application grows complex this becomes tedious to manage.

For example:-

    <RestaurantInfo />
    <RestaurantAlbums />

In the above example we can have 4 api calls:
1) <RestaurantInfo /> component making one api call for getting basic information about a Restaurant

2) <RestaurantAlbums /> api to fetch all the images of that Restaurant
3) <RestaurantReviews /> api to fetch all reviews
4) <RestaurantReviewDetail /> api to fetch some details around those individual reviews like comments, likes etc.

The problem with the above code structure is that we need to somehow manage the loading state and data fetching states for all those api calls that are happening above.

So what is the solution?

For the above problem we have multiple solutions which can be as follows:

  • Delegate all api calling logic into the parent container and let all of them wait until all data fetching is complete and pass data to child components as props. The problem with this approach is now the parent needs to be aware of all api calls which are needed by child components and also maintain a complex state for all these api responses.
  • Make all the child components smart/stateful components and let each of them manage their own loading and data states. This is complex since converting a stateless component to a stateful component is not something we would want to do.
  • The third solution is using Suspense

With Suspense it works differently. How?

With suspense and react-cache, we can use our same functional component and still fetch data from it.

The difference here being instead of fetching data from a lifecycle method like

we will fetch this data from inside of

How is this even possible?

This becomes possible using react-cache and suspense

Now a word of caution,

is still unstable and it’s implementation or api might change over time.

An example of how to use react-cache to create a restaurant list fetching resource:-

import {
} from "react-cache";

const restaurantListResource = unstable_createResource(() => {
  return new Promise((resolve, reject) => {
      .then(res => res.json())
      .then(response => {
        const { restaurants } = response;


In the above code snippet we are using unstable_createResource and as the name suggests this is still


unstable_createResource takes a function as one of its arguments and a hash function as the second argument which is used to create the key for the hash map which caches the data.

The whole suspense and suspended rendering magic comes into play with this unstable_createResource because this function throws a promise.

(Dan’s tweet about cache throwing a promise and react catching it)

A layman implementation of what it might look like could be:

const unstable_createResource = (method) => {
  let resolved = new Map();
  return {
    read(key) => {
      if (!resolved.has(key)) {
        throw method(...args)
          .then(val => resolved.set(key, val));
      return resolved.get(key);

If you notice, it returns an object with a read function which takes key as a param which is usually the hash key of the hash map and if the data is not fetched yet then this read function will throw a promise as we see on line no 6.

The actual implementation of this function can be found here:-


Who will catch this promise?

Error Boundaries will catch this promise like how they used to catch the error thrown by React render.
More information on Error Boundaries can be found on reactjs.org:

So now with unstable_createResource our RestaurantList component would look something like this:

const RestaurantList = () => {
  // if no restaurants are found in the cache, the suspense will throw a promise
  const restaurants = restaurantListResource.read();
  // this line will have to wait until that promise resolves
  return (
      <h2 className="f3 fw4 pa3 mv0">Restaurant List</h2>
      <div className="cf pa2">{renderRestaurants(restaurants)}</div>

Who will implement componentDidCatch?

This is where Suspense from react comes into play. React.Suspense has a componentDidCatch sort of mechanism which will catch this promise and show a fallback until the promise is resolved.

import React, { Suspense } from 'react';

const RestaurantListContainer = props => {
  return (
    <Suspense fallback={'Loading...'}>
      <RestaurantList />

This concludes the topic of using React.Suspense to suspend rendering until data fetching is complete and until then show a fallback. We learnt about react-cache in this topic and how it can be used to throw a promise and suspend rendering.

Concurrent React

To take advantage of the asynchronous capabilities of concurrent React, We change the way we render our root

<App />

Where we do this in standard React:

ReactDOM.render(&lt;App /&gt;, document.getElementById('root'));

We do this for concurrent React:

ReactDOM.createRoot(document.getElementById('root')).render(&lt;App /&gt;);

That is all that needs to be changed to enable Concurrent React.

This brings us with a new magical capability which is:-

prop- this is the time in ms after which our fallback component will show up. This will avoid screen flickering issue which usually occurs on faster network where the loader shows up for few ms and then the data comes immediately. This will make sure that for faster networks Spinner will never show up thereby avoiding screen flickering.


If you are developing in React 16.6, what has been recommended is to wrap <React.StrictMode> around <App /> so any unsupported features you may integrate will be prompted as warnings in your development console.

Wrap strict mode around your app like so:

   <App />
</React.StrictMode>, document.getElementById('root'));

Defer Mode in Concurrent React

We can defer certain setState calls and let it wait until some other important operations like data fetching finishes for example clicking on a restaurant card and not rendering the detail page until all the data for the detail page has been loaded.

This is the kind of stuff it allows you to do:

To use this we need another unstable api which is part of an npm package called as


import { unstable_scheduleCallback as defer } from "<a href="https://www.npmjs.com/package/scheduler" target="_blank">scheduler</a>";

To defer a setState call we can do like the function below where I am delaying showing the detail page until the data for that page is loaded.

import { unstable_scheduleCallback as defer } from "scheduler";

toggleDetailPage = id => {
  if (id) {
      id: id
    defer(() => {
        showDetail: true
  } else {
      id: id,
      showDetail: false
Defer is also able to somewhat catch the thrown promises, and only apply the state changes after all of the child async operations are completed.

Complete example with concurrent react, createResource, Suspense and defer mode can be found here

Here is what Dan had to say about this whole set state defer:

Code Splitting with React.lazy and React.Suspense

The React.lazy function lets you render a dynamic import as a regular component.


import React from 'react';
import RestaurantListComponent from './RestaurantList';

function App() {
  return (
      <RestaurantListComponent />

Note: In the above implementation the RestaurantListComponent will be part of your main bundle and will not be lazy-loaded.


import React, { Suspense, lazy } from 'react';
const RestaurantListComponent = lazy(() => import('./RestaurantList'));// code-splitted, on demand loaded component

function App() {
  return (
    <Suspense fallback="Loading...">
      <RestaurantListComponent />

Note: With this approach, RestaurantListComponent will be a code splitted component loaded on demand.

Example of lazily loaded component in a chunk “1.chunk.js”

How to use these API’s?

React.Suspense with React.lazy is a stable API and can be installed from npm as the latest stable version of react and react-dom

npm install react react-dom

react-cache and scheduler are unstable. Here is how you can still use them:

npm install react@16.7.0-alpha.2 - next
npm install react-dom@16.7.0-alpha.2 - next
npm install react-cache@2.0.0-alpha.1
npm install scheduler@0.11.2


To conclude, I am really excited about all these api’s to be stable soon.
What are your thoughts on these features? Let me know in the comments section! 😊

Here is the roadmap from the React team for the upcoming releases:


Special thanks to Sara Vieira for reviewing this 😊

Vivek Nayyar Hacker Noon profile picture

@vivek-nayyarVivek Nayyar

Read my stories

👋 Senior Software Engineer with 5 years' of experience building products for numerous domains.


Join Hacker Noon

Create your free account to unlock your custom reading experience.