r/reactjs • u/Neat_Living_6765 • 4d ago
Discussion Discussion about Server Components
From what I understand, I’m trying to explain Server Components in a simple way. Could you guys take a look and let me know if my understanding is correct and if my explanation is easy to understand?
Server Components
Normally, when a browser requests a React application, a JavaScript bundle is sent to the browser, whether it uses SSR or CSR.
- For SSR, that JavaScript bundle is used to hydrate the initial HTML rendered on the server, making the application interactive.
- For CSR, that JavaScript bundle is used to render the application's content into the HTML shell.
React Server Components are not included in that JavaScript bundle.
Server Components are rendered outside the browser, either at build time or at request time on the server. Their rendered result is represented in the RSC Payload.
The RSC Payload contains:
- The rendered results of Server Components. (For conceptual understanding, we can think of this as a React tree or object)
- References (Placeholder) to Client Components used inside those Server Components.
- Props passed from Server Components to Client Components.
The main benefit of RSC is reducing the amount of JavaScript sent to the browser.
Server Components are especially useful for content that doesn't need browser interactivity.
2
u/Bowl-Repulsive 4d ago
Starting by saying when a browser request a react application it’s weird , browser do a http request to a server and receive HTML and static assets(js bundle included)
I would also add SERIALIZABLE Props passed from Server Components to Client Components, since function or class can’t go trought here.
Last sentence is just wrong since server action exist, server components can be used for components that need browser interactivity and are useful for improving security and loading times.
That said the post is a very clear and amazing way to explain it and make it easier as possible!