The React team is looking forward to sharing a few updates:

  1. We have launched React 18, our next major version.
  2. We have set up a working group to prepare the community for the gradual introduction of new features in React 18.
  3. We have released the React 18 Alpha library so that the authors of the library can try it out and give feedback.

These updates are intended primarily for third-party library administrators. If you learn, teach, or use React to build user applications, you can safely ignore this message. But you are welcome to follow the discussions in the React 18 working group if you are curious!

What happens in React 18

When released, React 18 will include ready – made enhancements (such as automatic dosing), new APIs (such as startTransition) and a new streaming server renderer with built-in support React.lazy.

These features are made possible by a new alternative mechanism that we will add to React 18. It’s called “simultaneous rendering,” and it allows React to produce multiple versions of the interface at the same time. This change is mostly behind the scenes, but it opens up new opportunities to improve the actual and perceived performance of your application.

If you’ve been following React’s future research (we don’t expect you to do that!), You may have previously heard something called concurrent mode or that it may break your application. In response to this feedback from the community, we have designed an upgrade strategy for phasing in. Instead of an all-or-nothing mode, simultaneous rendering is only possible for updates triggered by one new feature. In practice, this means that you can enable React 18 without rewriting and try out new features at your own pace.

Gradual acceptance strategy

Since the simultaneous use in reaction 18 is opt-in, there are no significant changes in the behavior of the components outside the package. You can upgrade to React 18 by changing your application code as little as possible or without any changes. The level of difficulty is comparable to a typical React release. Based on our experience with converting multiple applications to React 18, we expect many users to be able to upgrade within one afternoon.

We successfully posted concurrent features to tens of thousands of components on Facebook, and in our experience, we’ve found that most React components “just work” without further modification. We are committed to ensuring that this is a smooth update for the entire community, so today we announce the React 18 working group.

We’re trying something new for this release: We’ve invited a panel of experts, developers, library writers, and educators from the React community to participate React 18 working group give feedback, ask questions, and collaborate with the publication. We couldn’t invite all of our desires into this first, small group, but if this experiment succeeds, we hope there will be more in the future!

The goal of the React 18 working group is to prepare the ecosystem for the smooth and gradual deployment of React 18 in existing applications and libraries. Hosted by the working group GitHub chats and is readable by the public. Working group members can leave feedback, ask questions and share ideas. The core team will also use the discussion to share our research findings. As a stable release approaches, all important information will also be posted on this blog.

For more information about upgrading to React 18 or additional resources, see the article React 18 notification message.

Access to the React 18 working group

Everyone can read the conversations React 18 working group repo.

As we expect the team’s interest to begin, only invited members are allowed to create or comment on threads. However, the threads are fully visible to the public, so everyone has access to the same information. We believe this is a good compromise between creating a productive environment for team members while maintaining transparency with the wider community.

As always, you can send bug reports, questions, and general feedback to us monitoring the problem.

How to try React 18 Alpha today

The new alpha are published regularly using npm @alpha tag. These publications are built using our most recent commitment to our main repo. When a feature or bug fix is ​​combined, it appears as an alpha on the next day of the week.

There may be significant behavioral or API changes between Alpha releases. Remember it alpha publications are not recommended for user-oriented production applications.

Predicted React 18 release timeline

We don’t have a specific release date, but we expect it to take several months of feedback and iteration before React 18 is ready for most production applications.

  • Library Alpha: Available today
  • Public beta: At least several months
  • Release Candidate (RC): At least several weeks after Beta
  • General Availability: At least several weeks after RC

For more information on our projected release timeline, see available in the working group. We will post updates to this blog as we get closer to the public release.


Please enter your comment!
Please enter your name here