Introduction to React Data Fetching Course

Course Introduction

Going through the problems with useEffect

What’s Wrong With useEffect?

Going through the problems with other libraries

Using Libraries or Frameworks for Data Fetching

Optimizing Your Dev Environment for this Course

Understand the problems with using the useEffect hook for data fetching, the pros and cons of using libraries and frameworks for data fetching.

Intro & Getting Started

We will learn how to fetch data before the component loads

Fetch Data Before you Component Loads

Here we'll learn how to create an efficient data cache

Creating an Efficient Data Cache

We will learn how to fetch data on an event

Fetching Data on an Event

We'll learn how to handle loading and error states in our application

Loading and Error Handling

Here we're going to recap what we've learned in Module 2

Module 2 Recap

Learn the benefits of prefetching data, how to create an efficient cache data to prevent refetching and also how to handle data fetching on an event.

Prefetching & Caching

Here we'll take a look at how to refetch data in a simple way

Simple Refetching

Here we'll learn how to fix race conditions

Fixing Race Conditions

Here we'll learn how to fix network waterfalls

Fixing Network Waterfalls

Here we'll recap what we've learned in Module 3

Module 3 Recap

Learn how to identify and fix two big issues with data fetching in React, Race Conditions and Network Waterfalls.

Race Conditions & Network Waterfalls

Here we'll learn how to use the useSyncExternalStore hook

The useSyncExternalStore Hook

Here we'll learn how to prefetch data based on the route

Prefetching Based on Page Route

This lesson, focus on saving and reusing prefetched data sources efficiently using context and a custom data-loading function.

Saving Data Sources

Stale While Revalidate

Module 4 Recap

Learn how the useSyncExternalStore hook can be used to improve the performance of our data fetching library. We'll also implement the stale-while-revalidate caching method.

Refactoring and SWR

Fetching on the Server

Final Words

Learn about how our data fetching library can be used in a server-side environment particularly with React Server Components.

Wrapping Up

Learn how to create a **small, efficient data fetching library** that will prefetch, cache your data as well as handle **error and loading states**, and even implement a caching technique called **stale-while-revalidate**.

### The Problem with Data Fetching in React

Data fetching is such a crucial part of building React apps and **most developers are doing it incorrectly**.

This is primarily because there are many videos and tutorials that show you how to fetch data using the useEffect hook, but also, because the [React documentation suggests it](https://react.dev/reference/react/useEffect#fetching-data-with-effects).

But then goes on to specify [all the problems with using it](https://react.dev/reference/react/useEffect#what-are-good-alternatives-to-data-fetching-in-effects) such as:

- Effects don’t run on the server

- Effects makes it easy to create “network waterfalls”

- Effects usually means you don’t preload or cache data

- It’s not very ergonomic

So for small projects, maybe the useEffect hook is fine, but for medium to larger projects it definitely should not be an option for data fetching.

You could go ahead and use one of the many popular frameworks and libraries for doing this, but they have **a lot of features** and a lot of **magic behind the scenes** that you may not need.

Also, because they are libraries, you may not be able to **customise them to your specific needs**.

### How Does _This Course_ Help?

In this course you will learn how to build a data fetching library **from scratch**.

That's right, you'll start with an **empty file**, understand every single line of code that you write. And end up with a **single-file library** that will be able to; **prefetch and cache your data** in a performant way, **handle loading and error states**, and also implement a caching technique called **stale-while-revalidate**, which will refetch new data in the background while still showing the old data.

But that's not all...

This library will also address two big issues with data fetching in React, [race conditions](https://maxrozen.com/race-conditions-fetching-data-react-with-useeffect) and [network waterfalls](https://blog.sentry.io/fetch-waterfall-in-react/).

If you haven't heard or encountered these issues before, you're lucky. But in case you do, this library will have you covered.

No matter if you want to get a better understanding of how data fetching in React works, if you want to build a custom data fetching solution for your next project, or if you want to build the next [TanStack Query](https://tanstack.com/query/latest), this course will help you do all those things and much more.

### Course Content Overview
Course Overview: Total Modules: **5** Total Lessons: **20** Total Video Runtime: **2 hours, 40 minutes**

Implement prefetching, caching and stale-while-revalidate with the useSyncExternalStore hook

This course will teach you how to fetch in a performant way for React without relying on a third-party library or the useEffect hook. We will build a custom data fetching library from scratch that will prefetch, cache, and address all the common issues with fetching data.

React Data Fetching: Beyond the Basics

A Solution to Network Waterfalls & Race Conditions

Implement the Stale While Revalidate technique

How React re-renders when data is fetched

What the problems are with using useEffect to fetch data

The pros and cons of using **libraries and frameworks for data fetching**

How to start fetching data **before your React component loads**

How to create a **data cache** to prevent data being refetched

How to identify and fix **Network Waterfalls and Race Conditions**

When and why to use the **useSyncExternalStore hook**

How tin implement the **stale-while-revalidate** caching method

How data fetching for **React Server Components** can be achieved

In this lesson, we will explore the concept of fetching data before a component loads also known as pre-fetching. We will discuss the importance of pre-fetching, especially for large apps or slow internet connections, and how it can improve performance.

 hook in React, data fetching only occurs after the component has been mounted. This means that the component will render first before the data fetching process begins. This may not cause any noticeable performance issues for users with a decent internet connection or for small apps. However, for larger apps or users with slower internet connections, users may see a loading spinner for longer than they expect. Pre-fetching resolves this issue by fetching data before the component mounts, meaning the data could be ready before the component renders.

To demonstrate the pre-fetching process, let's consider a simple Pokemon List app that fetches data from the 

 hook. The app displays the fetched data and allows users to view details for specific Pokemon.

 has worked each time I've tested it, but it's a public API and may be subject to changes or downtime. If you encounter issues with the API, you can use a different API or mock the data locally.

Before diving into the pre-fetching implementation, let's briefly examine the code structure of the app by starting with the 

// package.json file
{
  "name": "poke-app",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0",
    "preview": "vite preview"
  },
  "dependencies": {
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "devDependencies": {
    "@types/react": "^18.2.43",
    "@types/react-dom": "^18.2.17",
    "@vitejs/plugin-react": "^4.2.1",
    "eslint": "^8.55.0",
    "eslint-plugin-react": "^7.33.2",
    "eslint-plugin-react-hooks": "^4.6.0",
    "eslint-plugin-react-refresh": "^0.4.5",
    "vite": "^5.0.8"
  }
}

In order to focus on data fetching the project does not contain any third party packages, just what is provided by default from 

 component for basic routing, as well as a 

 components for the homepage and details page. The homepage contains two console logs to help to see when the component loads and when the data loads.

// Home.jsx

function Home() {
 const [pokemons, setPokemons] = useState(null);

 useEffect(() => {
   console.log("data loads"); // <- console log 1
   getPokemons().then(setPokemons);
 }, []);

 console.log("component loads"); // <- console log 2
 if (!pokemons) {
   return <div>Loading...</div>;
 }

 // remaining code...
}

 These aren't necessary but help to illustrate the fact that with useEffect data loading happens after the component is mounted.

 The API folder holds the logic for fetching Pokemon data which we won't go into detail here.

 component is wrapped in a component called 

// main.jsx
// Module imports

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

---
title: Fetch Data Before you Component Loads
description: We will learn how to fetch data before the component loads
privateVideoUrl: https://stream.mux.com/DGNr5dU2C3IKW00bGt4YY52KXfxhRTDZbYYlG7nWkw5k.m3u8
isPublicLesson: true
code: https://gitlab.com/fullstackio/books/newline-course-apps/richard-bray-create-a-custom-usefecther-component-in-react-app/-/tree/main/02.01
---

# Fetch Data Before you Component Loads

In this lesson, we will explore the concept of fetching data before a component loads also known as pre-fetching. We will discuss the importance of pre-fetching, especially for large apps or slow internet connections, and how it can improve performance.

When using the `useEffect` hook in React, data fetching only occurs after the component has been mounted. This means that the component will render first before the data fetching process begins. This may not cause any noticeable performance issues for users with a decent internet connection or for small apps. However, for larger apps or users with slower internet connections, users may see a loading spinner for longer than they expect. Pre-fetching resolves this issue by fetching data before the component mounts, meaning the data could be ready before the component renders.

## Example: Pokemon List App

To demonstrate the pre-fetching process, let's consider a simple Pokemon List app that fetches data from the [PokéAPI](https://pokeapi.co/) using the `useEffect` hook. The app displays the fetched data and allows users to view details for specific Pokemon.

:::caution

The [PokéAPI](https://pokeapi.co/) has worked each time I've tested it, but it's a public API and may be subject to changes or downtime. If you encounter issues with the API, you can use a different API or mock the data locally.

:::

### Code Structure

Before diving into the pre-fetching implementation, let's briefly examine the code structure of the app by starting with the **package.json** file.

```json
// package.json file
{
  "name": "poke-app",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0",
    "preview": "vite preview"
  },
  "dependencies": {
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "devDependencies": {
    "@types/react": "^18.2.43",
    "@types/react-dom": "^18.2.17",
    "@vitejs/plugin-react": "^4.2.1",
    "eslint": "^8.55.0",
    "eslint-plugin-react": "^7.33.2",
    "eslint-plugin-react-hooks": "^4.6.0",
    "eslint-plugin-react-refresh": "^0.4.5",
    "vite": "^5.0.8"
  }
}
```

In order to focus on data fetching the project does not contain any third party packages, just what is provided by default from [Vite](https://vitejs.dev/).

 The source folder contains a **Route** and **Link** component for basic routing, as well as a **Home** and **Details** components for the homepage and details page. The homepage contains two console logs to help to see when the component loads and when the data loads.

```jsx {7,11}
// Home.jsx

function Home() {
 const [pokemons, setPokemons] = useState(null);

 useEffect(() => {
   console.log("data loads"); // <- console log 1
   getPokemons().then(setPokemons);
 }, []);

 console.log("component loads"); // <- console log 2
 if (!pokemons) {
   return <div>Loading...</div>;
 }

 // remaining code...
}
```