Web Components offer reusable, framework-agnostic UI building blocks, but how well do they work with Server-Side Rendering (SSR)? With evolving standards like Declarative Shadow DOM, new possibilities emerge, yet challenges remain. This talk explores strategies, trade-offs, and the future of SSR with Web Components, assessing their viability in enterprise environments.

Thanks to their encapsulation and cross-platform re-usability, Web Components are changing the way we build for the web, yet using them with React has been challenging so far. In this talk, we will address the growing adoption of Web Components, focusing on the integration hurdles in React and the upcoming support with React 19.

I’ve been building UI components with React for a while now, and I’ve read a lot about server-side rendering (SSR). From what I’ve read, I didn’t expect SSR to affect how React components are built.

Lately, I’ve been working on a component library, and one of the consumer teams I worked with uses SSR. After building many components, I received feedback that several of them weren’t working correctly when SSR was used. This got me thinking about why this was happening and how SSR might affect building React components.

A real-world deep dive into React Server Components (RSC) and server actions—what they enable, their challenges, and why debugging RSC payloads can be a nightmare. Expect an honest take on RSC’s strengths and limitations.