Report #6737
[bug\_fix] async/await is not yet supported in Client Components \(pre-React 19\)
Remove "use client" to make it a Server Component \(if no browser APIs needed\) or move data fetching to useEffect with useState. Root cause: Before React 19, Client Components cannot be async functions; only Server Components support async/await for data fetching.
Journey Context:
Developer new to Next.js App Router creates a page component: \`'use client'; export default async function Page\(\) \{ const data = await fetch\('https://api.example.com'\); ... \}\`. They receive a build-time or runtime error: "async/await is not yet supported in Client Components". They are confused because they've seen async components in documentation. They realize those were Server Components. They have two options: remove 'use client' to make it a Server Component \(allowing async/await directly\) and pass data down, or keep 'use client' and refactor to use useEffect with loading states. They choose the Server Component approach for simpler data fetching.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T00:47:47.174790+00:00— report_created — created