Hi everyone!
This week, we're delighted to finally have a preview of React Server Components support in React Router. I've also found some very interesting PRs on the React repo, and give you a glimpse of what could be coming soon!
The React Native ecosystem is surprisingly calm, but no doubt they keep everything secret for App.js Conf next week!
By the way, I would really appreciate your support. Now that I'm automatically removing cold subscribers, the newsletter is decreasing over time 😅. Any retweet, like, engagement, or testimonial really helps me! Please convince your friends to subscribe ❤️
💡 Subscribe to the official newsletter to receive an email every week!
Cut React Code Review Time & Bugs in Half
Code reviews are critical but time-consuming. CodeRabbit acts as your AI co-pilot, providing instant Code review comments and potential impacts of every pull request.
Beyond just flagging issues, CodeRabbit provides one-click fix suggestions and lets you define custom code quality rules using AST Grep patterns, catching subtle issues that traditional static analysis tools might miss.
CodeRabbit has so far reviewed more than 5 million PRs, installed on 1 million repositories, and used by 50 thousand Open-source projects. CodeRabbit is free for all open-source repo's. Get started today!
⚛️ React
React Router RSC Preview
The React Router team unveiled a preview of React Server Components support using the Parcel bundler. Stable support is blocked until Vite officially supports RSCs, but the good news is that React Router is becoming more framework-agnostic, and they expect to support other bundlers in the future with minimal effort.
The feature is designed to be both incrementally adoptable by returning JSX in loaders/actions, but also to feel good on new greenfield projects looking to go all-in with Server Component Routes, ’use client’ and ’use server’ directives. They also explain how to solve the N+1 query problem in RSCs, inspired by GraphQL/DataLoader.
Render Hooks and With React
Looks like the Render Props pattern is making a comeback, with 2 new projects proposing to expose React core hooks in a render callback. This is a convenient trick in some situations, allowing you to "inline" a component while still respecting the rules of hooks, but it does not really solve any problem that can’t be solved by extracting a custom component. An interesting pattern to use sparingly.
💸 Product for Engineers - What engineers get wrong about communication
👀 React Core PR - createStore() skeleton API: Initial scaffolding work to implement the Concurrent Stores feature mentioned in the latest React Labs update. There’s no implementation yet, but I still find it interesting to check the signature/types of this upcoming API that should support both ad-hoc state updates and the reducer/actions pattern. What strikes me the most is that you can’t access the store value directly, apart from using the use(store) API, and this totally makes sense in a concurrent world. Remember, this is a work in progress, and things may change.
👀 React Core PRs - <SuspenseList> being actively worked on: It’s been a while since we last heard of this upcoming component that we thought would be in React 18. It allows to coordinate Suspense boundaries and control their “reveal order” (forwards/backwards/together).
👀 React Core PR - Transition indicator + onDefaultTransitionIndicator API: A feature being worked on should allow giving user feedback while React transitions are in progress. The default React-DOM implementation should show a native browser spinner, but it’s possible to opt out or provide a custom feedback.
👀 SWC PR - Initialize @swc/react-compiler: A new package to integrate the React Compiler for all SWC-based projects is coming. It will still use Babel under the hood (details), but it’s possible to optimize by only running it on relevant files (see what Next.js is doing), potentially using parallelization.
👀 Next.js PR - Initial Segment Explorer devtool: The Next.js team started working on a tool to help you visualize parallel and interception route segments.
🔐 Next.js Race Condition to Cache Poisoning - CVE-2025-32421: Low-severity Pages Router vulnerability, already patched.
📣 Appwrite Sites: The open-source Vercel alternative: The AppWrite cloud platform can now deploy full-stack React meta-frameworks. It positions itself as a direct Vercel competitor, although there are differences (containers vs serverless). It’s a paid cloud product, but you can also self-host it for free.
📜 Concurrent Rendering: Free interactive lesson on React transitions from the ui.dev course.
📜 Correctly infers from initial props: You don’t need to explicitly type your context value and can leverage type inference instead.
📜 Making Next.js Navigation Fast af: Using React Router within your Next.js app works, but I doubt it’s a good idea, doesn’t permit you to use RSCs, and is likely to cause trouble if you use different routers on different pages.
📜 Mastering Focus Management in React with flushSync: By default, React uses batching and doesn’t flush state updates immediately to the DOM, and you can opt out of this behavior when needed.
📜 Preserving and Resetting State in React: Explains why conditionally wrapping a component may make it reset its state.
📜 Just F***ing Use React: Entertaining read, also exists in a less profane Just Use React variant.
📜 The Past and Future of Render Optimization with React Context
💸 Full-Stack Upgrade – Build real apps with auth, orgs & file uploads: The Road to Next is your next step as a full-stack React developer.
📦 Waku 0.23 - Fine-grained component render modes: Makes it possible to statically pre-render parts of a dynamic page. I find the API a bit confusing, but the idea looks cool and simpler than Next.js Partial Pre-Rendering.
📦 React-Scan 0.3.4 - Scan for React performance issues: A release that takes the opportunity to announce upcoming features and the availability of the extension on the Chrome store.
📦 React Aria - May 19 Release
📦 React-Admin - May 2025 Update - 5.7 & 5.8
📦 StyleX 0.13 - New defineConsts and positionTry APIs
📦 Shopify Hydrogen 2025.05 - Upgrades to React Router 7
🎥 Theo - React Is the last framework: Probably a quite controversial point of view that React runtime/syntax is less likely to change now (mainly due to AI). Innovation is moving an abstraction layer above with the React Compiler.
🎥 Alem Tuzlak - Server Componets (RSC) in react-router are... actually good?
🎙️ Syntax 902 - Fullstack Cloudflare with React and Vite - RedwoodSDK with Peter Pistorius
🎙️ Front-end Fire 95 -TanStack DB & The Rise of the Tannerverse
Add loyalty logic to your product — with just one API.
Why build loyalty from scratch when you can plug it in with Dynamo?
Dynamo is the API-first headless loyalty engine used by product teams at leading fintech and consumer apps to embed rewards, tiers, and behavior-based engagement — without writing it all from zero.
With 250+ cloud data integrations, a React and React Native SDK, plus a clean sandbox trial, you can improve your retention now in days not months.
→ Launch demo and get free sandbox access now.
📱 React-Native
🔀 Other
👀 TC39 - Agenda for the 108th meeting: Next week, another set of interesting proposals for JS could progress, some of them could become part of the standard: using keyword, Error.isError().
📜 JavaScript's New Superpower: Explicit Resource Management: Describes the using keyword mentioned above, already available in Chrome, and more importantly, in Node 24.
📜 The Future of MCP is GraphQL: Apollo announcing their MCP server, explaining the alignment between GraphQL and AI needs.
📜 I think the ergonomics of generators is growing on me
📜 Reports of Deno's Demise Have Been Greatly Exaggerated
📦 Node 22.16 - node.config.json support (experimental)
📦 Zod 4.0 - faster, slimmer, more tsc-efficient, new Zod Mini export, localization and more
📦 Remotion Media Parser - Universal lib based on WebCodecs to parse/decode/encode videos
🤭 Fun
See ya! 👋
