What changed and why it fixes the error

• blog-section.tsx is now a pure Server Component that only renders props and does not create Promises. It receives posts from the parent page (or uses safe defaults). This avoids creating Promises in a Client Component render path. 1
• featured-projects.tsx is an async Server Component that fetches data with await on the server, which is supported and streamed by React/Next.js. No promises are created in client land. 12
• app/blog/page.tsx fetches posts on the server with await and renders them directly. No client-side promise creation.

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

• Preview / and /blog to confirm the error is gone
• Add a loading state with Suspense if you want streaming UX
• Implement blog search and categories
• Add author profiles and SEO metadata for blog posts

Why this fixes it

• Both BlogSection and FeaturedProjects are now Server Components that fetch with async/await on the server. No Promises are created inside a Client Component or hook, so React won’t warn about “uncached promise” during client rendering. 2
• If you pass data from a Server Component down to a Client Component, it stays safe because the Promise is resolved on the server before rendering on the client. If you ever need to read a Promise in render, use React’s use API within a Suspense boundary, but prefer server-side data fetching in the App Router. 12

If you still see this error elsewhere, look for:

• "use client" components that call async functions during render or in hooks for data fetching. Move those fetches to a Server Component, or use a Suspense-ready cache/library.

Actions

• Preview /
• Preview /blog
• Convert any remaining data-fetching Client Components to Server Components
• Add Suspense fallbacks if you intentionally stream nested sections

Sources:

• React use API and Suspense guidance for reading Promises in render 12