


Showcase of a Lightweight Hook for Async Data Fetching & Caching in React
Jan 07, 2025 pm 06:36 PMHey everyone!
I’ve been working on a lightweight React hook that I called useAsync that mimics some of the essential features of React Query (like fetching, caching, retries, etc.) but in a more compact, easily customizable package. Below is a quick breakdown of how it works internally, referencing the relevant code sections. If you want to see the entire code, head over to the repo:
Full Source Code on GitHub.
The hook is also available on npm as api-refetch.
Why Making My Own Hook?
While React Query and SWR are both great libraries, I wanted a more hands-on approach for a few reasons:
Lightweight Footprint
While React Query and SWR are feature-rich, they can be relatively large (React Query ~2.2 MB, SWR ~620 kB). api-refetch is around 250 kB, making it ideal for smaller apps where bundle size is a big concern. This hook as meant to be installed as a dependency of another library (Intlayer). As a result, the size of the solution was an important consideration.Easy to Customize & Optimize
I needed some specific capabilities—like storing/fetching data from local storage and managing parallel requests using a straightforward approach.
By cloning the repo or copying the code directly into your project, you can strip out any unwanted features and keep only what you need. This not only reduces bundle size but also minimizes unnecessary re-renders and increase, giving you a leaner, more performant solution tailored to your specific requirements.No Required Provider
I wanted to avoid Context Provider to make the hook global, and keep it's usage as simple as possible. So I made a version of the hooke based on a Zustand store (see example bellow).Learning Exercise
Building an async library from scratch is an excellent way to understand concurrency, caching, and state management internals.
In short, rolling my own hook was a chance to hone in on precisely the features I need (and skip the ones I don’t) while keeping the library small and easy to understand.
Covered Features
The React hook manage:
- Fetching & State Management: Handles loading, error, success, and fetched states.
- Caching & Storage: Optionally caches data (via React states or Zustand under the hood) and offers local storage support.
- Retries & Revalidation: Configurable retry limits and automatic revalidation intervals.
- Activation & Invalidation: Automatically activates and invalidates queries depending on other queries' or states. Example: automatically fetch some data when the user logs in. And invalidate it when the user logs out.
- Parallel Component Mount Fetching: Prevents multiple simultaneous requests for the same resource when multiple components mount at once.
How the Code Works
Below are the key points in api-refetch and short references to the relevant parts of the code in useAsync.tsx.
1. Fetching and Handling Parallel Mounting
- Code Snippet:
// This map stores any in-progress Promise to avoid sending parallel requests // for the same resource across multiple components. const pendingPromises = new Map(); const fetch: T = async (...args) => { // Check if a request with the same key + args is already running if (pendingPromises.has(keyWithArgs)) { return pendingPromises.get(keyWithArgs); } // Otherwise, store a new Promise and execute const promise = (async () => { setQueryState(keyWithArgs, { isLoading: true }); // ...perform fetch here... })(); // Keep it in the map until it resolves or rejects pendingPromises.set(keyWithArgs, promise); return await promise; };
- Explanation: Here, we store any ongoing fetch in a pendingPromises map. When two components try to fetch the same resource simultaneously (by having the same keyWithArgs), the second one just reuses the ongoing request instead of making a duplicate network call.
2. Revalidation
- Code Snippet:
// Handle periodic revalidation if caching is enabled useEffect( () => { if (!revalidationEnabled || revalidateTime <= 0) return; // Revalidation is disabled if (!isEnabled || !enabled) return; // Hook is disabled if (isLoading) return; // Fetch is already in progress if (!isSuccess || !fetchedDateTime) return; // Should retry either of revalidate if (!(cacheEnabled || storeEnabled)) return; // Useless to revalidate if caching is disabled const timeout = setTimeout(() => { fetch(...storedArgsRef.current); }, revalidateTime); return () => clearTimeout(timeout); }, [ /* dependencies */ ] );
- Explanation: Whenever you enable revalidation, api-refetch checks if the cached data is older than a specified revalidateTime. If it is, the data is automatically re-fetched in the background to keep your UI in sync without extra manual triggers.
3. Retry Logic
- Code Snippet:
useEffect( () => { const isRetryEnabled = errorCount > 0 && retryLimit > 0; const isRetryLimitReached = errorCount > retryLimit; if (!isEnabled || !enabled) return; // Hook is disabled if (!isRetryEnabled) return; // Retry is disabled if (isRetryLimitReached) return; // Retry limit has been reached if (!(cacheEnabled || storeEnabled)) return; // Useless to retry if caching is disabled if (isLoading) return; // Fetch is already in progress if (isSuccess) return; // Hook has already fetched successfully const timeout = setTimeout(() => { fetch(...storedArgsRef.current); }, retryTime); return () => clearTimeout(timeout); }, [ /* dependencies */ ] );
- Explanation: On error, the hook counts how many failed attempts have occurred. If it’s still below the retryLimit, it automatically waits retryTime milliseconds before trying again. This process continues until data is successfully fetched or the retry limit is reached.
4. Auto-Fetch
- Code Snippet:
// Auto-fetch data on hook mount if autoFetch is true useEffect( () => { if (!autoFetch) return; // Auto-fetch is disabled if (!isEnabled || !enabled) return; // Hook is disabled if (isFetched && !isInvalidated) return; // Hook have already fetched or invalidated if (isLoading) return; // Fetch is already in progress fetch(...storedArgsRef.current); }, [ /* dependencies */ ] );
- Explanation: With autoFetch set to true, the hook will automatically run the async function as soon as the component mounts—perfect for “fire-and-forget” scenarios where you always want the data on load.
See the Full Source on GitHub
Check out the complete code, which includes local storage logic, query invalidation, and more here:
- Full Source Code
Feel free to give it a try, report issues, or contribute if you’re interested. Any feedback is much appreciated!
Example of use
Installation
Copy the code or code the (repo)[https://github.com/aymericzip/api-refetch]
Or
// This map stores any in-progress Promise to avoid sending parallel requests // for the same resource across multiple components. const pendingPromises = new Map(); const fetch: T = async (...args) => { // Check if a request with the same key + args is already running if (pendingPromises.has(keyWithArgs)) { return pendingPromises.get(keyWithArgs); } // Otherwise, store a new Promise and execute const promise = (async () => { setQueryState(keyWithArgs, { isLoading: true }); // ...perform fetch here... })(); // Keep it in the map until it resolves or rejects pendingPromises.set(keyWithArgs, promise); return await promise; };
Quick Example
// Handle periodic revalidation if caching is enabled useEffect( () => { if (!revalidationEnabled || revalidateTime <= 0) return; // Revalidation is disabled if (!isEnabled || !enabled) return; // Hook is disabled if (isLoading) return; // Fetch is already in progress if (!isSuccess || !fetchedDateTime) return; // Should retry either of revalidate if (!(cacheEnabled || storeEnabled)) return; // Useless to revalidate if caching is disabled const timeout = setTimeout(() => { fetch(...storedArgsRef.current); }, revalidateTime); return () => clearTimeout(timeout); }, [ /* dependencies */ ] );
That’s it! Give it a try, and let me know how it goes. Feedback, questions, or contributions are more than welcome on GitHub.
GitHub: api-refetch
Happy coding!
The above is the detailed content of Showcase of a Lightweight Hook for Async Data Fetching & Caching in React. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

PlacingtagsatthebottomofablogpostorwebpageservespracticalpurposesforSEO,userexperience,anddesign.1.IthelpswithSEObyallowingsearchenginestoaccesskeyword-relevanttagswithoutclutteringthemaincontent.2.Itimprovesuserexperiencebykeepingthefocusonthearticl

Event capture and bubble are two stages of event propagation in DOM. Capture is from the top layer to the target element, and bubble is from the target element to the top layer. 1. Event capture is implemented by setting the useCapture parameter of addEventListener to true; 2. Event bubble is the default behavior, useCapture is set to false or omitted; 3. Event propagation can be used to prevent event propagation; 4. Event bubbling supports event delegation to improve dynamic content processing efficiency; 5. Capture can be used to intercept events in advance, such as logging or error processing. Understanding these two phases helps to accurately control the timing and how JavaScript responds to user operations.

The main difference between ES module and CommonJS is the loading method and usage scenario. 1.CommonJS is synchronously loaded, suitable for Node.js server-side environment; 2.ES module is asynchronously loaded, suitable for network environments such as browsers; 3. Syntax, ES module uses import/export and must be located in the top-level scope, while CommonJS uses require/module.exports, which can be called dynamically at runtime; 4.CommonJS is widely used in old versions of Node.js and libraries that rely on it such as Express, while ES modules are suitable for modern front-end frameworks and Node.jsv14; 5. Although it can be mixed, it can easily cause problems.

JavaScript's garbage collection mechanism automatically manages memory through a tag-clearing algorithm to reduce the risk of memory leakage. The engine traverses and marks the active object from the root object, and unmarked is treated as garbage and cleared. For example, when the object is no longer referenced (such as setting the variable to null), it will be released in the next round of recycling. Common causes of memory leaks include: ① Uncleared timers or event listeners; ② References to external variables in closures; ③ Global variables continue to hold a large amount of data. The V8 engine optimizes recycling efficiency through strategies such as generational recycling, incremental marking, parallel/concurrent recycling, and reduces the main thread blocking time. During development, unnecessary global references should be avoided and object associations should be promptly decorated to improve performance and stability.

There are three common ways to initiate HTTP requests in Node.js: use built-in modules, axios, and node-fetch. 1. Use the built-in http/https module without dependencies, which is suitable for basic scenarios, but requires manual processing of data stitching and error monitoring, such as using https.get() to obtain data or send POST requests through .write(); 2.axios is a third-party library based on Promise. It has concise syntax and powerful functions, supports async/await, automatic JSON conversion, interceptor, etc. It is recommended to simplify asynchronous request operations; 3.node-fetch provides a style similar to browser fetch, based on Promise and simple syntax

The difference between var, let and const is scope, promotion and repeated declarations. 1.var is the function scope, with variable promotion, allowing repeated declarations; 2.let is the block-level scope, with temporary dead zones, and repeated declarations are not allowed; 3.const is also the block-level scope, and must be assigned immediately, and cannot be reassigned, but the internal value of the reference type can be modified. Use const first, use let when changing variables, and avoid using var.

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

DOM traversal is the basis of web page element operation. Common methods include: 1. Use parentNode to obtain the parent node, and can be chained to find it upward; 2. children return a collection of child elements, accessing the first or end child elements through the index; 3. nextElementSibling obtains the next sibling element, and combines previousElementSibling to realize the same-level navigation. Practical applications such as dynamically modifying structures, interactive effects, etc., such as clicking the button to highlight the next brother node. After mastering these methods, complex operations can be achieved through combination.
