Google's modern-web-guidance skill against a real React app

Google's modern-web-guidance skill against a real React app
14 minutes by Ahmad Alfy

AI coding tools often suggest outdated frontend patterns because their training data lags behind the web platform. Google Chrome's modern-web-guidance tool addresses this by letting you search a curated set of best-practice guides before writing code. Tested against a real React app, it caught missing dark mode declarations, forms lacking native submission handling, and stale validation approaches, while correctly flagging which existing code was already sound. Its most useful feature is tying browser support advice to concrete Baseline dates, so you know exactly when a pattern is safe to ship without a fallback.

Cut AI Coding Token Costs by up to 36% with Sonar Vortex
sponsored by Sonar

Sonar Vortex operates inside your AI coding agent’s inner reasoning loop, supplying deep architectural context before code is written, then verifying the output in real time. In testing, software defects dropped by 92% and token consumption decreased. Build safer code while spending less on LLM calls.

React doesn't need a state management tool. Then I built one.
9 minutes by Štěpán Granát

Štěpán explains why most React apps do not need a state management library, but some complex cases benefit from centralized state. He introduces react-arven, a small library that combines existing React state without creating another state source. It uses selectors and stable actions to reduce unnecessary re-renders while keeping React’s familiar hooks and context model.

Experimenting with RSCs for performance and UX in Next.js
23 minutes by Aurora Scharff

Aurora explores how React Server Components can improve performance and user experience in Next.js. She shows how to keep data fetching and rendering on the server while using small client components for interaction. Her examples include loading more posts, streaming search results, and server-rendered message previews. She also explains how URLs, Suspense, and Server Functions can create fast, responsive interfaces.

Making referential stability a type
9 minutes by Jovi De Croock

Inline arrays and callbacks passed to memoized components cause silent re-renders that are hard to catch. Jovi's experiment adds a branded type called Stable that marks a reference as guaranteed to survive unrelated renders. Strict wrappers for React and Preact hooks then reject unstable dependencies at the exact line where they appear, with an error message explaining how to fix it. The goal is to move that contract from comments and lint rules into the type system itself.

We stopped using RSC on TanStack
7 a minutes by Tanner Linsley

TanStack stopped using React Server Components after making its markdown and code-rendering tools much smaller. React Server Components had improved performance by keeping large dependencies off the client, but it also added architectural complexity. With smaller packages, regular server-side rendering became simpler while keeping the site fast. The experience suggests React Server Components is useful for heavy server-side work, but it should not be used when simpler solutions are enough.

And the most popular article from the last issue was:

• Advanced React state boundaries in a real Next.js app