I remember reading about how different CDNs deal with caching, specifically around shared caches/propagating caches between different POPs/edges. Does anyone have a good resource or insights?
So what I'm wondering is when you hit a cold edge, what happens? Does the request go straight to origin or check if it's cached elsewhere in the CDN first? Does the cached value propagate to other edges? I think this differs between CDNs and specific cases?
I wonder if render props breaks with React Server Components? Imagine a server component returning this:
<ClientComponent>{(propSetInClientRender) => <ServerComponent prop={propSetInClientRender} />}</ClientComponent>
Seems like this must be invalid?
Two other notes.
1. In a practical sense it's true streaming isn't as widely supported as we'd like. But we need to make the right tradeoffs long-term, and creating demand wouldn't hurt.
2. Now that most of core work is done, we'll be focusing on making CM easier to adopt.
🆕 An Annotated Guide to React Server Components
dev.to/swyx/an-annotated-gui…
My recap of everything I've learned about @reactjs Server Components in the last 2 days, informed by following Concurrent React over the last 2 years.
I'll have more and deeper takes on React Server Components, but for now I'll just say that I love how they embrace composition.
Composition really is the React models superpower, but is still sadly underutilized. Highly related to this is nested routing.
Nested routing really seems more or less required to fully utilize RSCs, how else could you match deeply nested RSCs? Remix is well positioned here of course, but I'm sure Next.js has a plan as well, will be interesting to see what happens there.
Shout-out to @sugarpirate_, an amazing engineer y'all should be following. She's really blown me away this year with her work spanning the React family!
Things like this is why I'm rooting for Remix as a complement to existing frameworks. Solving long standing deficiencies in current SSR without waiting for a next gen renderer, while staying close to the React model.
Nested routes are a very powerful abstraction to build on top.
📦Today marks the release of hoofd 1.0.0
This library aims at providing a set of hooks to set the html head tags (meta, title, ...).
Hope you enjoy!
The hooks are currently documented in the README. github.com/JoviDeCroock/hoof…
New Pure CSS/HTML drawing. Made for Chrome. And this one you can alter without even using DevTools! No JS, no SVG.
Inspired by video game character customization screens, and 90s couture.
diana-adrianne.com/purecss-c…
Prefetch data with React Query and NextJS – #CodeWithSwiz
What I love about this is that it doesn't feel clunky. Gatsby's useStaticQuery is fantastic, but components need to know aobut it.
Here the client component has no idea it's being prefetched 😍
swizec.com/blog/prefetch-dat…