What changed and why it fixes the error
If you still need client-side fetching in the future, wrap it with a Suspense-compatible library (e.g., useSWR) or a Suspense boundary as appropriate. 2 But the App Router strongly favors moving fetches to server components by default. 1
Actions
Why this fixes it
If you still see this error elsewhere, look for:
Actions
Sources: