#569 – August 09, 2026
how to manage state across the boundaries of a modern Next.js app
Advanced React state boundaries in a real Next.js app
11 minutes by Nir Tamir
Nir describes how to manage state across the boundaries of a modern Next.js app. He covers URL state, browser APIs, TanStack Query caches, React Server Components, client context, and optimistic updates. The main lesson is to clearly define who owns each piece of state, how React should react to changes, and how different parts of the application stay synchronized.
Still manually testing your React app? Hire Mo, the AI QA that catches bugs for you.
sponsored by Momentic
Your agents ship more code than your team can review and test. Mo explores your app on web, iOS, or Android and bug bashes it the way a human would. Every bug it files comes with a recording and repro steps. No scripts to write or maintain. A Fortune 1000 enterprise pointed it at staging and caught 27 bugs. Join the waitlist to run your first bug bash.
React 19 useActionState explained
13 minutes by Shubhra Pokhariya
React 19's useActionState hook replaces the repetitive pattern of manually managing form submission state. Pass it an action function and an initial state, and it returns the current state, a form action, and a pending flag. The biggest production mistake is using a local pending flag instead of the built-in one, which can let users queue duplicate submissions. Shubhra suggests skipping it for optimistic updates, multi-step wizards, or anything not tied to a form.
Generative user interface
13 minutes by Boda Zhao
Generative UI replaces walls of AI text with dynamic interface elements that adapt to what users actually want. Three approaches exist: static components mapped from tool results, declarative JSON specs, and open-ended code generation inside sandboxed iframes. These are not mutually exclusive, and production apps will likely combine all three.
Async hydration in Preact
7 minutes by Jovi De Croock
Preact already supports async hydration through Suspense boundaries, letting parts of a page become interactive independently rather than all at once. Hydration 2.0, coming in Preact 11, makes this more reliable by marking exact DOM ranges in server HTML, fixing edge cases where the wrong nodes were targeted.
Evaluation for coding agents on realistic React work
10 minutes by Million Software
Existing benchmarks let models pass every test while still writing React code that breaks in production. ReactBench was built to catch what tests miss, like performance, accessibility, and code quality issues. The benchmark targets React specifically because it powers around 70% of JavaScript-based websites, meaning small model mistakes can spread fast.
And the most popular article from the last issue was: