Skip to main content
Version: 4.5

Fetch then Render

A core design feature of Rest Hooks is decoupling actual data retrieval from data usage. This means hooks that want to ensure data availability like useRetrieve() or useResource() actually only dispatch the request to fetch. NetworkManager then uses its global awareness to determine whether to fetch. This means, for instance, that duplicate requests for data can be deduped into one fetch, with one promise to resolve.

Another interesting implication is that fetches started imperatively via useFetcher won't result in redundant fetches. This is known as 'fetch then render,' and often results in an improved user experience.

These are some scenarios where this pattern is especially useful:

Fetch-then-render can be adopted incrementally. Components using data can useResource() and be assured they will get their data when it's ready. And when fetch-then-render optimizations are added later - those components don't need to change. This makes data usage tightly coupled, and fetch optimization loosely coupled.

Route preload example

In most cases the best time to pre-fetch data is at the routing layer. Doing this makes incorporating all of the above capabilities quite easy. Here we'll walk through a small demo that incorporates concurrent mode with SuspenseList, and useTransition(). However, it would be quite easy to extend this to also support server side rendering and code splitting routes with paraellel data and code loading.

See full demo here

Resource Definitions

export class PostResource extends SlowFetchResource {
readonly id: number | undefined = undefined;
readonly userId: number | null = null;
readonly title: string = '';
readonly body: string = '';

pk() {
static urlRoot = '';

export interface Address {
readonly street: string;
readonly suite: string;
readonly city: string;
readonly zipcode: string;
readonly geo: {
readonly lat: string;
readonly lng: string;

export class UserResource extends SlowFetchResource {
readonly id: number | undefined = undefined;
readonly name: string = '';
readonly username: string = '';
readonly email: string = '';
readonly phone: string = '';
readonly website: string = '';
readonly address: Address | null = null;

pk() {
static urlRoot = '';


This is a preload hook for one route. It returns a function that will load the data needed for that route.

import { useCallback } from 'react';
import { useFetcher } from 'rest-hooks';
import { UserResource, PostResource } from 'resources';

function useFriendPreloader() {
const fetchUser = useFetcher(UserResource.detailShape(), true);
const fetchPosts = useFetcher(PostResource.listShape(), true);
// ideally we could also fetch the comments for each post at this point
// however, the API has no solution to this, so we have to have one cascade
// waterfall here.

// Alternative API designs include nesting, HTTP/2 server push, and an endpoint
// to fetch comments based on a user rather than post.

return useCallback(
(friendId: number) => {
fetchUser({ id: friendId });
fetchPosts({ id: friendId });
[fetchUser, fetchPosts],

Components using data


const FriendCard = () => {
// useData gets the route context
const { friendId } = useData();
const friend = useResource(UserResource.detailShape(), { id: friendId });
// render some JSX


Here we use \<SuspenseList /> and useResource()

const Posts = () => {
// useData gets the route context
const { friendId } = useData();
const posts = useResource(PostResource.listShape(), { userId: friendId });

// By using a SuspenseList here, we can guarantee that posts
// appear in the optimal viewing order, despite separately loading comments.
// Using "forwards" and "collapsed", we always see earlier loaded posts before later,
// but never later loaded posts before earlier. This avoids the page "popping"
// as it resizes with the comment section.
// Suspsense lets us "unlock" the title and body of the first post, but avoid
// showing other posts or having to wait for all the comments to load to display.

// I've also chunked posts to appear two at a time inside a Suspense boundary.
// This is mostly to explore the possibilities of Suspense - displaying data
// exactly on our terms, rather than merely when the network returns.

// LOOK: Uncomment / recomment the Suspense boundaries in Posts and Post to
// see how boundaries at different layers can affect users.
// Remove the SuspenseList and see how much jankier it looks!

const chunkedPosts = chunk(posts, 2);

return (
<div className="flex flex-wrap -mx-4">
<SuspenseList revealOrder="forwards" tail="collapsed">
{[post1, post2]: any) => (
<React.Fragment key={}>
{post1 && (
<div key={} className="w-1/2">
<Post post={post1} />
{post2 && (
<div key={} className="w-1/2">
<Post post={post2} />


To make things easier, routing libraries could adopt two properties defined for each route - the component information (either a path or function to load it) and a hook like this that returns a function to call to preload.

In our example we're just scrapping together a very redimentary routing layer. This is not very extensible but demonstrates incorporating preloading with useTransition()

To see all of this in context check out the demo.

function App() {
// where we store the route
const [friendId, setFriendId] = useState(1);
const [startTransition, isPending] = useTransition(SUSPENSE_CONFIG);
const preload = useFriendPreloader();

// effectively route change trigger
const changeFriend = useCallback(
friendId => {
// This becomes more meaningful when you start code splitting and load
// load with suspense as well. Then you don't have to wait on the code
// loading to start the data fetch.
// This delays commiting the React tree with new friendId until
// suspense is resolved.
startTransition(() => {

const context = {
friendId: friendId,
changeFriend: changeFriend,

return (
FallbackComponent={props => {
return <span>Error</span>;
<DataContext.Provider value={context}>
<Suspense fallback={null}>
{/* Null fallback means less intermediate loading spinners */}
<Core />