What can you do with Server Components and Actions in React 19? Let’s talk about how React 19’s features are a big deal, even for a simple marketing site.

Anja Petry

HTML

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

React 19 introduces Server Components that allow developers to choose where their code runs, fetch data directly within components, and improve performance. Actions, on the other hand, provide convenient features like isPending state, error handling, and optimistic UI. These new features make it easier to build marketing websites and enhance the developer experience in React 19.

React 19 lets you write impossible components

React Server Components are ideal for:
<ol>
<li>Reducing client-side bundle sizes by offloading component logic to the server.</li>
<li>Fetching data directly within components, leading to simplified code.</li>
<li>Enhancing performance by rendering components on the server.</li>
</ol>
Avoid using Server Components when:
<ol>
<li>Immediate client-side interactivity is needed, as they can’t handle client-side state or effects.</li>
<li>High-frequency updates are required, since server round-trips can introduce latency.</li>
<li>You’re working in environments where server-side rendering isn’t feasible or beneficial.</li>
</ol>

Interesting… I thgouth React was born to rely on the client rather than the server, but here we are…

A few more years of catching up with Svelte &amp; SvelteKit, and it may only be a few years behind. Very glad to not have to use React!

Focus on hybrid apps seems like a waste of effort to me.
Any performance gain from server side rendering is not worth the overhead cost of hosting.
Server side rendering should only be used when it is undoubtably necessary for SEO and security. If you can, keep client side and server side code separate to reduce project complexity.

And you still calling it a “Library”