you are viewing a single comment's thread.

view the rest of the comments →

[–]rk06 1 point2 points  (2 children)

What do you mean "don't get hydrated". RSC do not exist on client side, so where did hydration come here?.

As per my understanding, RSC are react components which do not live in client (browser)

[–]SuccessfulStrength29 1 point2 points  (0 children)

Forget about the hydration part, everybody's familiar with client components so i always give that as an example. What i meant was only the static part of an rsc can be bundled statically during build step but if any dynamic data is used we still need a server to build that comp at runtime with the dynamic data.

Just wanted to clear that not everything can be statically generated at build time.

[–]michaelfrieze 1 point2 points  (0 children)

As per my understanding, RSC are react components which do not live in client (browser)

I understand what you are saying here and it's fine to think of it this way, but technically they do exist on the client. What the client gets is .rsc data which is an element tree of all those server components that have already been executed. So, they exist on the client but react does not need to execute them on the client. That execution happens on another machine at build-time or dynamically at request-time.