React 19 Released: Actions, the use API, and Stable Server Components

What happened

React 19 became stable on December 5, 2024, as announced on the official React blog. It is a substantial release that formalises several patterns the React team had been developing, most notably a new approach to handling asynchronous state updates called Actions, and it makes React Server Components support stable.

Actions

A very common pattern in React apps is to perform a data mutation and then update state in response, which historically meant manually juggling pending states, errors and optimistic updates. React 19 adds support for using async functions inside transitions to handle these automatically. By convention, functions that use async transitions are called Actions. Actions manage the pending state for you, support optimistic updates through the new useOptimistic hook, provide built-in error handling, and integrate with forms so that a function can be passed directly to a form's action prop.

New hooks and the use API

Building on Actions, React 19 introduces useActionState to handle the common cases, and in react-dom adds form Actions plus useFormStatus so design-system components can read the status of a parent form without prop drilling. The release also adds the use API, which can read a promise, suspending until it resolves, or read context conditionally, including after an early return, something the older useContext could not do.

Stable Server Components

React 19 includes all the React Server Components features that had been maturing in the Canary channel. Server Components allow rendering components ahead of time, in an environment separate from the client bundle or the SSR server, which can run at build time or per request. With React 19, libraries can target it as a peer dependency using the react-server export condition in frameworks that support the full-stack React architecture.

Why it mattered

React 19 reduced the amount of manual plumbing developers write for common asynchronous UI patterns, and it gave the ecosystem a stable target for Server Components. For teams, the practical impact is less boilerplate around forms and data mutations, and a clearer foundation for frameworks that blend server and client rendering. The React team published a dedicated upgrade guide alongside the release for teams moving from React 18.

Related on Skillo

See also: React 18 and concurrent rendering.

Sources

• React v19 (official React blog)
• React 19 upgrade guide (official)

Published date reflects the original event date (2024-12-05). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.