Loading video...

Video Failed to Load

Go Home

❌ Avoid resolving a promise in a server component and block rendering. ✅ Resolve the promise in the client side with `Reac.use()`

47,215 views • 1 year ago •via X (Twitter)

10 Comments

George Moller's profile picture
George Moller1 year ago

I've been working professionally with React for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video tutorials just like this one. Check them out ↓

React Universe Conf | Sept 2-4, 2025's profile picture
React Universe Conf | Sept 2-4, 20251 year ago

React Universe is a constantly evolving ecosystem—driving curiosity and continuous learning. And that's what we love about it! 🙌 Join us at React Universe Conf 2025 to future-proof your dev team:

pavi2410's profile picture
pavi24101 year ago

nextjs problems require nextjs solutions

Thibaud Dervily's profile picture
Thibaud Dervily1 year ago

I think this can impact SEO, am I wrong?

Ali Bey's profile picture
Ali Bey1 year ago

Doesn’t resolving a promise in RSC happen only at buildtime? So it will not block the rendering in this case.

Alfon's profile picture
Alfon1 year ago

typo, React.use()

Nicholas Ly's profile picture
Nicholas Ly1 year ago

Can't you just make `User` a server component and do the fetch there? You can still wrap `User` with Suspense and it'll function the exact same—no need for `React.use()`.

Josh's profile picture
Josh1 year ago

Why have the server component in this scenario? It seems entirely redundant

Javed's profile picture
Javed1 year ago

Why passing to the client when you can still make the fetch call on server and at the same time use suspense with it Just need to create a wrapper around the client components

Debo.dev's profile picture
Debo.dev1 year ago

How does this affect security?

Related Videos