Wow! Join a panel discussion with top React experts such as @dan_abramov, @acemarke, @alessbell, @ephemjs, and @mweststrate. They will discuss ➡️Open Source & "perceived competition" between projects.
📣 Join the conference to attend!
If you need another incentive to try out the v5 release candidate: I promise to jump on any issue you have with it and help you fix it.
Once v5 is released, I'll expect too many devs to try it out, I won't have time for everything. And some decisions are then irreversible, too.
To get a better understandig of data fetching approaches in #React, I built a simple example application with three different stacks:
- @nextjs
- @tan_stack query (suspense)
- ts query and React Router with loaders and actions
ICYI: here is the source: github.com/nilshartmann/reac…
I acknowledge and apologise for my timeline pretty much being just a series of vague niche stuff that should probably be long format blog posts instead..
So I wrote about why I think React.memo is worse than the other alternatives that exist to improve performance in a React app:
tkdodo.eu/blog/the-uphill-ba…
📢 Vite-plugin-ssr is now called Vike 🔨
A new era for the project.
🛠️ Official integrations vike-{vue,react,solid} while keeping core flexible
🚀 Next-gen scaffolder
💫 (Upcoming) marketing overhaul targeting a broader audience
@brillout @charles_jo21000 @AurelienLourot
📢 TanStack Query v5 is now available as a release candidate 🎉
This means we're pretty close to shipping it "as-is", unless you find and report things. There has never been a better time to try out v5 than RIGHT NOW
github.com/TanStack/query/re…
I finally have a full draft done for the React Query SSR docs rewrite. I haven't done a final once-over yet so there might be embarrassing mistakes, but I would love your feedback and suggestions!
github.com/TanStack/query/pu…
💯 My instinct for a long time was that we should try to achieve full component data co-location. Today with RSCs I'm convinced "section" based prefetching is the best tradeoff, but that we are investing too little effort into just making that more ergonomic/predictable.
Manual prefetch is fine. It's only a little bit of duplication. It is just easy to not do it and get hit, but I suppose the solution is easy as well. Wish there was a way to give optimal default path. But I keep landing at preloaders which look an awful lot like loaders. 3/3
.@ephemjs, freelance consultant, is thrilled to invite you to #React Advanced London 🎉
"It'd be a pretty practical talk where I give you a step by step directions for how you can migrate existing app over to start using #ServerComponents in an incremental fashion the demo app."
🎈 Holding this news back has been killing me, but I’m so excited I finally get to share it with you. I get to work with with my friends on @partykit_io! blog.partykit.io/posts/every…
I'll be giving a talk about Migrating to Server Components at @ReactAdvanced October the 20th.
If you want to watch, you can register via my badge to join remotely: portal.gitnation.org/badges/…
There's a lot of great speakers, don't miss out!
Has anyone built a good testing library for testing streaming SSR, Server Components etc yet? Or has any good examples to look at (besides the React tests)?
Use case is testing library code.
The React team is looking to create a FAQ on server components. Here are a few questions we're starting with:
Why are server components the default?
Do server components require a server? (hint: no)
What other questions should be in a React Server Component FAQ?