Mark Dalgleish (@markdalgleish) 's Twitter Profile
Mark Dalgleish

@markdalgleish

🦄 CSS Modules co-creator / 💿 @remix_run + React Router at @shopify / @MelbJS organiser / 🧁 Vanilla Extract / dad x4

ID: 257765996

calendar_today26-02-2011 03:41:25

24,24K Tweet

72,72K Followers

0 Following

Mark Dalgleish (@markdalgleish) 's Twitter Profile Photo

The lightbulb moment for me with RSC support in React Router was realising that, to me, it’s not about server components. The real win is that frameworks can become much more portable, decoupled from specific bundlers. RSC handles bundler stuff, frameworks handle the runtime.

Mark Dalgleish (@markdalgleish) 's Twitter Profile Photo

SSR when using React as a library: - Function you call on your SSR server - Function you call in the browser RSC when using React Router as a library: - Function you call on your RSC server - Function you call on your SSR server - Function you call in the browser

Mark Dalgleish (@markdalgleish) 's Twitter Profile Photo

Huge shout out to Parcel for pioneering the RSC APIs that made this possible. It’s had a big influence on us, and now the Vite implementation too.

MJ (@mjackson) 's Twitter Profile Photo

React Router takes a unique approach to React Server Components. It’s “guts out” meaning each piece of the process is exposed. You can easily hook into how the React client calls the React server, for example. The whole system is designed to be as accessible as possible.