Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

47,215 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von George Moller
George Mollervor 1 Jahr

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 ↓

Profilbild von React Universe Conf | Sept 2-4, 2025
React Universe Conf | Sept 2-4, 2025vor 1 Jahr

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:

Profilbild von pavi2410
pavi2410vor 1 Jahr

nextjs problems require nextjs solutions

Profilbild von Thibaud Dervily
Thibaud Dervilyvor 1 Jahr

I think this can impact SEO, am I wrong?

Profilbild von Ali Bey
Ali Beyvor 1 Jahr

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

Profilbild von Alfon
Alfonvor 1 Jahr

typo, React.use()

Profilbild von Nicholas Ly
Nicholas Lyvor 1 Jahr

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()`.

Profilbild von Josh
Joshvor 1 Jahr

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

Profilbild von Javed
Javedvor 1 Jahr

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

Profilbild von Debo.dev
Debo.devvor 1 Jahr

How does this affect security?

Ähnliche Videos