The Suspense-Ready Ecosystem
What you'll learn: Which libraries and features actually work with Suspense today, and what still requires extra tooling.
The Current State of Suspense Support
Suspense is a powerful pattern, but it's not universally supported across the React ecosystem yet. Understanding what works now versus what requires framework integration helps you set realistic expectations.
What Works Out of the Box
React.lazy for code splitting is the poster child of Suspense support. It works perfectly without any additional setup:
const LazyComponent = React.lazy(() => import('./Heavy'));
<Suspense fallback={<Spinner />}>
<LazyComponent />
</Suspense>
This is production-ready and has been stable since React 16.6.
What Requires Framework Support
Data fetching with Suspense is the tricky part. While the Suspense component itself is ready, most data fetching libraries don't throw promises by default. To use Suspense for data:
- Frameworks like Next.js or Remix provide built-in Suspense-ready data fetching
- Libraries like Relay have native Suspense integration
- TanStack Query and SWR require opt-in configuration (experimental features)
- Custom fetching requires you to build a Suspense-compatible wrapper yourself
Think of it like this: Suspense is a power outlet that's been installed in your wall, but most appliances (data libraries) still need an adapter to plug into it.
The Opt-In Reality
Even mature libraries like TanStack Query have Suspense support behind experimental flags. This isn't a React limitation—it's that libraries need time to restructure around the "throw promise" pattern Suspense expects.
Key Takeaway: React.lazy works with Suspense today; data fetching requires either a Suspense-ready framework (Next.js, Remix), a library with explicit Suspense support (Relay), or opt-in experimental features in your existing tools.