Framework Support: Remix Deferred Data
You'll learn how Remix's defer() utility enables streaming responses that automatically trigger React Suspense boundaries for progressive rendering.
The Remix Streaming Model
Remix provides a built-in mechanism for Suspense-based data loading through its defer() loader utility. Instead of waiting for all data to load before rendering, you can immediately return critical data while streaming slower data chunks to the client as they become available.
How defer() Works
In a Remix loader, wrap slow-fetching promises in defer() without awaiting them:
// routes/dashboard.tsx
import { defer } from "@remix-run/node";
export async function loader() {
// Fast data - await it
const user = await fetchUser();
// Slow data - don't await, just pass the promise
return defer({
user,
analytics: fetchAnalytics(), // Promise, not awaited!
});
}
The Client-Side Bridge
Remix's <Await> component connects deferred promises to Suspense boundaries:
import { Await, useLoaderData } from "@remix-run/react";
import { Suspense } from "react";
export default function Dashboard() {
const { user, analytics } = useLoaderData<typeof loader>();
return (
<div>
<h1>Welcome, {user.name}</h1>
<Suspense fallback={<AnalyticsSkeleton />}>
<Await resolve={analytics}>
{(data) => <AnalyticsChart data={data} />}
</Await>
</Suspense>
</div>
);
}
The page renders immediately with user data, while the analytics section shows a skeleton until its promise resolves.
Key Takeaway: Remix's defer() and <Await> pair lets you stream server data progressively, triggering Suspense boundaries automatically for deferred promises—no custom "throw promise" logic required.