Agents ship React features faster than ever. They also ship unindexed queries, N+1s, and schema decisions made at 2am by a model that will never get paged.
Fortunately, agents can fix database problems too. They just need production data, and that's what the PlanetScale MCP server gives them. Hook up an agent, and the loop looks like this:
PlanetScale flags a slow query
The agent traces it back to the code in your repo
The agent opens a PR with the fix
You review and merge
Run it once, or put it on a schedule.
Underneath it all: the fastest, most scalable cloud Postgres and MySQL, with options like PlanetScale Metal when you need peak performance. Fast databases, fast React apps.
βStyleX, the atomic CSS-in-JS library from Meta, has been all the rage on X recently. This probably follows the π Cursor migration from Tailwind to StyleX. Or maybe itβs related to Meta open-sourcing Astryx, the extensible, agent-friendly design system built on top and powering thousands of their apps for years.
Anyway, we already covered all that, so here are the recent resources to check out:
π Styling Linear for the future with StyleX - Linear completed its styled-components to StyleX migration. They donβt explicitly mention Tailwind but still highlight where StyleX does better: strong type-safe constraints, deterministic and performant merging of styles, styling-at-a-distance deliberately hard.
π A deep dive into StyleX - Hands-on introduction and opinionated conclusion: Tailwindβs terse syntax is better for humans, while StyleX's stronger constraints are better for agents.
π React Types PR - Types for React 19.3 - We already had a hint of whatβs coming in the last issue. This DefinitelyTyped PR is still a draft but cautiously confirms the upcoming highlights. A new React DOM browser() API is coming. and will be stable for React DOM usage, designed to be extended by other platform/renderers, with React Native support likely coming later.
π React DOM Docs - New use(browser(reason)) API - This new API coming in v19.3 lets you mark a component as browser-only during server rendering. Must be called from a Client Component, within a Suspense boundary. Thereβs also a new onBrowserBailout() server API introduced for reporting.
ποΈ React Advanced London - π¬π§ London - 23 & 26 Oct. 40+ talks and 5+ hands-on workshops on modern React & AI tooling for React devs. A great place to catch up with the community - all inside London's historic ex-brewery. Save 10% on your ticket with code "TWIR".
π¦ Bun 1.4 - The Rust rewrite is ready, alongside so many other things that the blog post probably takes hours to read, so weβll focus on the React-related updates only. Built-in support for the React Compiler in Rust. A new Bun.markdown.react() turns Markdown into a React Element, supporting component substitution. Node.js compatibility improvements, Next.js 16 compatibility, reduced memory usage.
π¦ TanStack Query 5.102 - Simplify Query Methods - An important release for TanStack Query that finally implemented its RFC to merge 6 former imperative query methods under only 2 unified APIs: query() and infiniteQuery().
A passing test tells an agent how the run ended, not whether the code behaved as intended. Wallaby turns your JavaScript, TypeScript, and Python tests into a live runtime model the agent can inspect throughout the task.
Wallaby keeps results and coverage current as files change. With the Wallaby CLI for coding agents π€, agents can find tests covering a line, inspect branch coverage, follow one testβs execution path, and query runtime values in its exact context, without temporary logs or digging through terminal output.
Use Wallaby with Codex, Claude Code, GitHub Copilot, Cursor, Windsurf, and other agents locally, in containers, or in the cloud. Wallaby for coding agents is free for everyone during the beta.
React Native 1.0 is still on the horizon, but to respect Semantic Versioning, it first needs to clearly define its public API surface. Following the work on stable JS/TS and Java/Kotlin APIs, itβs now the turn of the C++ APIs to be clarified.
Until now, there has been no clear distinction between public and private C++ APIs. As a result, community libraries and frameworks sometimes depend on APIs that were never intended to be public. This can cause libraries to break when upgrading React Native, or force the core team to preserve backward compatibility for internal APIs to avoid breaking the ecosystem.
This RFC introduces a new three-tier visibility model for C++ APIs:
Public: Stable within major versions, safe for libraries to depend on, and exposed through a single umbrella header.
Framework: Stable within minor versions. Regular usage emits a suppressible warning.
Private: No stability guarantees. Regular usage emits a suppressible error.
Thereβs existing tooling to take a snapshot of existing C++ APIs, and it will be adapted to take into account this new visibility model. All this will greatly help stabilize the C++ APIs and ensure React Native doesnβt ship unintended breaking changes.
Work is already in progress to apply this visibility model to all C++ APIs. This will be rolled out gradually, first opt-in through a RN_STRICT_API build flag, then opt-out after a grace period, giving time for the public API consumers to migrate to the new umbrella headers. Most APIs have already been categorized, so if your library depends on private or framework APIs, now is probably a good time to chime in.
π React Native PR - ResizeObserver - A Web API spec-compliant implementation has been recently merged, but still behind a flag. More capable than onLayout.
ποΈ React Native Connection - π«π· Paris - 24 Sept. Last call to grab your ticket and join the React Native community in Paris! Get a 15% discount with code "TWIR".
π Pasting images into TextInput should not be this hard - Pasting an image into a chat input is surprisingly hard. Wrapping TextInput turned out to be the best decision to avoid reimplementing well-known behaviors and APIs.
π Gesture Handler's Touchable: The Button We Wish We Had Sooner - The old nice button components are deprecated and replaced with the new Touchable component. Per-state scale, opacity, and underlay with custom transition times. Hover support on mobile via mouse and pencil, all without writing a single animation.
π CSS - Class Prefix Selector - Not implemented anywhere yet, but CSS will support .prefix-* selectors, letting you target multiple CSS classes at once.
π¦ vgpu - WebGPU library, designed for agents - The creative library Vercel developed to ship performant shaders. Agents can verify their work with a CLI, even in sandboxes without a GPU.
π Read Online Hi everyone, Seb and Jan here! Back after a little break to cover news from the last two weeks. A lot is going on, apparently not everyone is on holiday because we still have many interesting releases, including many RCs from upcoming major versions. The native React Compiler rollout continues. React v19.3 seems around the corner. Plenty of TanStack Router/Start and Next.js content. React Native 0.87 is now out, paving the way for v1.0. ποΈ Weβll be taking another break next...
π Read Online Hi everyone, Kasia and Kuba from Software Mansion here. This week, Next.js 16.3 officially shipped, bringing Instant Navigations to the App Router and cutting dev server RAM usage by up to 90%. On the React Native side, a new, faster PlainText component and a deep dive into Vision Camera v5. Across the broader dev ecosystem, GitHub stacked PRs finally entered public preview with native base retargeting and a gh-stack CLI. Let's dive in! ποΈFYI: weβre taking a break next week; see...
π Read Online Hi everyone, Seb and Jan here π! This week we have an interesting React challenger, keeping its mental model but compiled ahead of time. Also various major announcements from the TanStack side. On the mobile side, we have interesting RN 0.87 PRs to look at, discussions around workers / worklets, a WebGPU/Skia integration, and React Navigation 8 / Screens 5 progress. Last week, many proposals progressed during a TC39 meeting. npm is going to scan for malware at publish time. Core...
