ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Expo Router lets you fetch data in server components during the build, but mixing them with client components changes trust boundaries and bundle behavior. This note helps you decide where to place data fetching and verify the result.
Learn how to eliminate client-side waterfalls in Next.js using Server Components, the extended Fetch API, and React Suspense for streaming HTML.
Decide where to place React Server Components and Client Components in Next.js, understand the serialization boundary, and validate with a build inspection.
Fetch data in Server Components and keep 'use client' limited to interactive leaf components to avoid client-side waterfalls and serialization errors.
nextjsserver-componentsTasadduq Burneyowner35.8K rep · 05 Jul 2025, 16:31 UTCLearn how to eliminate client-side waterfalls in Next.js by strategically placing Server Components and managing the serialization boundary between server and client logic.
React Server Components move data fetching into the component tree and eliminate API layers — but only if you respect the server/client boundary. A practical walkthrough with a blog index that streams posts from the database and keeps search interactive on the client.
Waku defaults to React Server Components for every route, turning only the smallest interactive widgets into client code. This post explains why, how file‑based routing shapes that boundary, walks through a filterable list example, and discusses trade‑offs you’ll need to manage.
The App Router's real win is awaiting data in Server Components with route-segment revalidation — but caching defaults changed across versions. A worked example and how to verify behavior on your install.
Use Next.js App Router Server Components with Suspense boundaries to stream a meaningful shell while slow data resolves in parallel. Keep secrets on the server, push client logic to leaves, and verify chunked transfer with curl.
waku
react