768: React 19 is here!

Episode Summary

Executive Summary: The episode breaks down React 19’s new beta release, focusing on major additions like actions/server actions, the new use API, improved Context usage, no-more-forwardRef, ref cleanup, document metadata hoisting, and script/style/preload handling. The hosts are generally positive, but question whether some problems were created by React itself and note that upgrade pain should be modest for most teams.

Main Topics: React 19 release and upgrade outlook: The hosts frame React 19 as a significant release after nearly two years, emphasizing that the beta gives library authors time to adapt and that most upgrades should be manageable. Actions, useActionState, and server actions: React 19 expands async actions, pending/optimistic/error handling, and server actions that can be imported directly instead of routed through API endpoints. The new use API and Suspense-driven data access: The use function can unwrap promises and consume context, simplifying some patterns, but currently depends heavily on Suspense support and lacks built-in caching in client usage. Context changes and state re-render concerns: Context now functions more directly with use, but it does not solve re-render propagation; the hosts contrast this with store-based approaches and mention React Forget as the long-term answer. Ref improvements and removal of forwardRef: React 19 simplifies DOM refs by allowing refs to be passed like normal props, eliminating the awkward forwardRef pattern and adding ref cleanup callbacks. Document metadata, styles, scripts, and preload support: Title, meta, link, style, and script tags can now be declared inside components and hoisted appropriately, which the hosts see as especially useful for component-level data and web components. Web component compatibility: React now scores 100% on Custom Elements Everywhere in the discussion, and the hosts see this as a major win for design systems and cross-framework reuse.

Key Arguments: React 19 is a meaningful release because it modernizes long-standing patterns and gives ecosystem maintainers time to verify compatibility via the beta. Server actions are valuable because they remove the need for API endpoints and route handlers in many flows, letting developers call server logic directly from components. The use API is promising for simpler Suspense-based data access, but without caching it is not broadly useful outside framework-integrated setups. React Context still suffers from re-render propagation, so React’s upcoming compiler work (React Forget) is needed to reach a more ergonomic model. Eliminating forwardRef makes component code cleaner and easier to read, especially in TypeScript-heavy codebases. Hoisting document metadata and assets from within components aligns React more closely with patterns the hosts like in Svelte and simplifies component-local concerns. React’s broader upgrade path appears low-risk because many breaking changes were deprecated years ago and React 18.3 can surface warnings first.

Data Points: Time since last major React release: almost two years - The hosts describe React 19 as the first major React release in nearly two years. Beta timing: dropped last week - Wes notes the beta had just shipped as of recording. Custom Elements Everywhere score: 100% - The discussion says React now scores 100% for web component support. Basic web component tests: 16 out of 16 - Wes mentions the basic test suite is fully passing. Advanced web component tests: 14 out of 16 - The advanced test suite is almost fully passing but not perfect. React 18.3: released - Suggested as the upgrade step before React 19 to surface deprecation warnings without breaking apps.

Pivotal Quotes: "There's a lot of really cool new features, a lot of cool stuff." — Scott Tolinsky: Opening framing of React 19’s overall significance. "There's no API endpoints. There's no route handlers. It's just a function you import and it runs." — Wes Bos: Explaining the appeal of server actions for checkout and other server-side workflows. "React is a little bit funkier." — Scott Tolinsky: Reflecting skepticism about React’s complexity compared with simpler async/component models.

Implications: React 19 reduces friction in forms, server logic, refs, metadata, and web components, but some new primitives still depend on future ecosystem tooling. Most teams should be able to upgrade gradually, with React 18.3 providing a warning-only stepping stone.