@bloodyaugust/use-fetch

A simple, safe fetch custom hook for React. Why safe? There's a good chance you've seen this before:

Warning: Can’t perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.

This hook helps you avoid mutating state on components that are unmounted by providing you with the mounted state of the hook, and aborts in-flight requests on unmount.

Features

• Safe: gives you the tools to avoid mutating state on unmounted components.
• Simple: Just a hook! No Contexts were harmed (or used) in the source of this library.
• Flexible: you get the response, the json, and of course the mounted state.
• Configurable: turn off automatic json parsing for those one-off cases.
• Provides a convenient Promise-based API.
• Aborts in-flight requests automatically if unmounted.
• Rejects Promise if the response indicates failure.
• No dependencies aside from React.

Install

1npm install @bloodyaugust/use-fetch
2# or, if using yarn
3yarn add @bloodyaugust/use-fetch

Usage

This example demonstrates how you might get some todos with useFetch while being sure you don't mutate state after your component is unmounted.

1import React, { useEffect, useState } from "react";
2import useFetch from "@bloodyaugust/use-fetch";
3
4function TodoList() {
5  const { execute } = useFetch();
6  const [todos, setTodos] = useState([]);
7
8  useEffect(() => {
9    const getTodos = async () => {
10      await execute("https://jsonplaceholder.typicode.com/todos/").then(
11        ({ json, mounted }) => {
12          if (mounted) {
13            setTodos(json);
14          }
15        }
16      );
17    };
18
19    getTodos();
20  }, []);
21
22  return (
23    <div>
24      {todos.map((todo) => {
25        <span key={todo.id}>{todo.title}</span>;
26      })}
27    </div>
28  );
29}

API

Props

1useFetch({
2  noJSON: bool, // Set true if you want to skip JSON parsing (no json key will be provided to the promise chain)
3});

Execute

execute is the function returned for invoking your fetch. It provides as consistent an API as it can, but there are some slight differences depending on if the request is successful, aborted, or failed for some other reason.

Parameters are the same as fetch.

success

1useFetch('https://jsonplaceholder.typicode.com/todos/')
2  .then({
3    response, // The fetch Response object
4    json, // The result of response.json() (not present if the noJSON prop was set)
5    mounted // The mounted state of the hook
6  } => {})

error with fetch (includes abort)

1useFetch('https://jsonplaceholder.typicode.com/todos/')
2  .catch({
3    error // The Error object thrown by fetch
4  } => {})

response indicates failure (!response.ok)

1useFetch('https://jsonplaceholder.typicode.com/todos/')
2  .catch({
3    response,
4    error, // new Error(`Request failed: ${response.status}`)
5    mounted
6  } => {})

Completed

completed is a ref returned from the hook to allow for determining the completion state of the fetch. It starts as false, but becomes true when the request completes for any reason (including abort).