Skip to content

React Native shares an update on the New Architecture rollout

updated

The React Native team has published a progress report on rolling out the New Architecture (the Fabric renderer and the TurboModule system) to the open source community. The post covers a new working group, a migration guide, an opt-in template switch in the upcoming 0.68 release, support for library authors, release process changes, and plans for Hermes.

A working group on GitHub

The team launched the React Native New Architecture Working Group, a discussion-only GitHub repository meant to coordinate the rollout across the ecosystem. Anyone can read it, but posting is limited to approved users to keep conversations focused. Developers can apply, or nominate someone else, through a form linked from the announcement.

Migration Guide merged

The Migration Guide, formerly known as the Playbook, has been merged and is available in the working group. It walks through creating a custom Fabric component or a TurboModule step by step, and explains how to adapt an existing app or library. The team also points to the Architecture section of the React Native website, including the Fabric section on the rendering pipeline, and asks for feedback on the documentation.

Opt-in switch in the 0.68 template

React Native 0.68.0, described as close to release, is the first version whose new app template includes an opt-in switch for the New Architecture. The template ships with comments and documentation intended to make it usable without extra reading.

To enable it on iOS, run RCT_NEW_ARCH_ENABLED=1 bundle exec pod install inside the ios folder. On Android, set the newArchEnabled property to true by one of these methods:

  • Edit the corresponding line in android/gradle.properties
  • Set the environment variable ORG_GRADLE_PROJECT_newArchEnabled=true
  • Invoke Gradle with -PnewArchEnabled=true

The app can then be launched with yarn react-native run-android or run-ios with Fabric and TurboModules enabled. The team asks developers to report bugs and unexpected behavior.

Third-party libraries

The post acknowledges that migration depends on library maintainers. Library authors are invited to post their migration status in the working group, and library users can request migrations there. If a library becomes a blocker for many users, the team says it will try to contact the maintainer. Software Mansion is highlighted for releasing a version of react-native-screens that supports both architectures, along with a blog post describing that migration.

Release process

With 0.68, release work moved to an internal rotation backed by improved documentation, discussions started with partners about a Copilot rotation, and community Release Supporters and Testers helped fix crucial bugs and regressions, especially around the New Architecture. The process will be refined further for 0.69.

Hermes as default engine

With the New Architecture, Hermes will become the default JavaScript engine, and new documentation and templates will have it enabled. Other engines such as JSC remain supported, but Hermes must be explicitly disabled to use them. The team is also working to align Hermes releases more closely with React Native releases, so that each React Native version ships with a fully compatible bundled engine and Hermes fixes reach users faster. In the post's words: "If you haven’t tried Hermes yet, now is the time to give it a go."

Source: reactnative.dev