Can RSCs Make Next.js Feel Faster?
Experimenting with RSCs for Performance and UX in Next.js
The post shows how moving more work to the server can reduce client-side JavaScript and improve loading speed. It uses real examples like search, "load more", and previews to show how this can work in practice
⚡️ Sponsor: Tigris Data
Bucket sharing. Without the IAM guessing game.
One button. One teammate. Exactly the access you intended. Stop writing bucket policies and get back to shipping.
📙 Articles / Tutorials / News
PR: Add ReactDOM browser() API
A new react-dom API called browser() lets components intentionally pause during SSR, then continue rendering in the browser. It’s designed for client-only UI that you don’t want rendered on the server
Next.js offline-support
Next.js is testing a new feature to make apps work better when the internet drops. Instead of showing errors right away, things like navigation, data loading, and Server Actions can wait and try again once the connection is back.
How to find a Next.js memory leak in production
The post points to three open framework leaks in recent Next.js versions, explains how each one shows a different memory growth pattern, and shows how heap snapshots can help you tell whether the problem is in Next.js or in your own code
📦 Projects / Packages / Tools
Lifeline
A polished timeline component for showing a life, company, or journey over time. It uses a horizontal, scroll-driven layout on desktop and a vertical one on mobile, and supports events, photos, people, badges, and even small effects. It ships as a shadcn registry item
shadscan – Deterministic UI audits for shadcn apps
A handy tool that scans a shadcn-based React app and gives its UI a score out of 100, along with clear evidence for every issue it finds.
next-nuke
At first glance this sounds like a simple delete command, but it does more than that: safer checks, dry runs, confirmation prompts, monorepo support, cache-only cleaning, Turbo cache clearing, and optional reinstalling
mobx@7.0.0
MobX is a popular state management library for React apps. Version 7 is a cleanup-focused major release that also makes the library smaller, with the production ESM bundle dropping from 17.02 KiB gzip to 13.96 KiB gzip. It removes a lot of old, long-deprecated features, including ES5 fallbacks, legacy decorators, and several older React helper APIs
Sponsor the newsletter
If you’re building something for the Next.js community, consider sponsoring this newsletter and putting it in front of 7,100+ Next.js developers.
🌈 Related
React’s programming model, compiled
Octane is a new framework that keeps the React style many of us already know, but compiles things ahead of time for speed. Its main ideas are no virtual DOM, no rules of hooks, and no manual dependency arrays, since the compiler figures that out for you.
The Absolute State of Management
The author argues that libraries like Redux, Zustand, and Jotai do not truly manage state. Instead, real state management needs better support for syncing changes over time
Props, Composers, and Providers: the composition pattern we're converging on
A practical look at how to structure React components: start with plain props, move to compound components when prop lists get too long, use composers and providers when the same UI needs different data sources, and only lift state when it truly needs to cross component boundaries
Weaponizing And Defending The React Flight Protocol: Deserialization Sinks In RSCs
The article walks through the Flight wire format, the meaning of its special prefixes, how the React2Shell exploit worked, and why some risks may be structural rather than one-off bugs
Have a link you want to share? Send me an email at erfan@nextjsweekly.com
All submissions are appreciated.
👋 See you next week!