When your kid starts humming along to your lame old person music.

Why's Discord gotta out me like that.

For those interested in RSC in Vite 👀

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.

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

`const statusCode = …` ☝️ constant `const STATUS _CODE = …` ☝️ constant, but louder

So excited we got this out.

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.

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.

You can tell I was raised well because I just thanked an LLM without asking for anything else.

I love it when PRs I’m working on quietly build a little fanbase.