Summary

React 18 is the next major release. The team published an alpha and created a React 18 Working Group to coordinate a gradual, opt-in rollout of new capabilities such as concurrent rendering, automatic batching, startTransition, and a streaming server renderer with built-in React.lazy support. The release is targeted first at library authors and maintainers; application authors can upgrade with minimal changes.

Key Points

• Release strategy: concurrent rendering is opt-in and only enabled for updates triggered by new APIs, enabling gradual adoption without rewrites.
• Alpha availability: React 18 alphas are published to npm under the @alpha tag for library authors to test; alphas may change frequently and are not production-ready.
• New features to try: automatic batching, startTransition API, and a new streaming server renderer that supports React.lazy.
• Working Group: GitHub Discussions host a public-read Working Group where invited members can comment; the repo will share research and migration guidance.
• Upgrade effort: no significant out-of-the-box breaking changes expected; many apps can upgrade with minimal effort (often within an afternoon in team's experience).
• Projected timeline: alpha available now; public beta in several months; RC and GA follow after additional weeks of testing and iteration.

Recommended actions for engineers

• Library maintainers: install the @alpha builds, run tests, and report issues to help stabilize APIs before beta.
• App teams: follow Working Group updates and plan upgrade experiments in non-production branches; adopt new APIs incrementally.
• Operators: do not use alpha builds in production; expect behavioral changes between alpha releases and prepare to test across releases.

Links & resources

• React 18 Working Group: GitHub Discussions (public read, invited contributors can comment).
• Alpha builds: npm @alpha tag.