React Compiler is a build-time tool that auto-memoizes React components and hooks, removing most hand-written useMemo and useCallback calls. It hit 1.0 stable in October 2025 and is compatible with React 17 and up. The grid below tracks where the compiler is actually wired into the framework, build tool, or runtime today - versus where integration is still landing. Rows distinguish official, first-party support from community-maintained loaders and in-progress SWC/oxc work.
Implementation notes
Expo opt-in flag
Expo SDK 54+ ships the Babel wiring automatically, but the compiler still requires "experiments": { "reactCompiler": true } in the app config. New apps do not get it on by default - the flag is mandatory until Expo promotes it out of experiments.
Next.js SWC fast-path
Next.js runs the React Compiler through the Babel plugin but layers a custom SWC analyzer in front of it so only files with JSX or hooks are compiled. The optimization activates automatically once reactCompiler: true is set. The React team recommends Next.js 15.3.1 or newer to pick up this fast path; current 16.x continues to ship it as stable.
Webpack: community loader only
There is no first-party webpack integration. The react-compiler-webpack loader is what the React docs point to, but it is community-maintained and outside the official release pipeline. Use it knowingly.
SWC and oxc work is still in flight
A standalone SWC plugin and the oxc/rolldown integration are both in active development. Next.js consumes an SWC fast-path internally, but the general-purpose SWC plugin is not yet stable, and oxc support is announced but unreleased.
Annotation / opt-in mode
Every integration that exposes a config surface supports compilationMode: "annotation" plus the "use memo" / "use no memo" directives. This is the safe rollout path for large existing codebases - turn the compiler on in annotation mode and opt components in file-by-file.
Methodology
Each row reflects what the project's primary source says about React Compiler integration: official installation pages, release notes, and changelogs. Status values follow a fixed taxonomy:
stable - documented, generally available, no flag required beyond the standard config option. beta - supported but gated behind an experiments/flag namespace. experimental - community or in-development integration without a stable contract. planned - announced by the maintainers but not released. unknown - no first-party documentation could be located.
Rows are re-verified against the linked source on each refresh. A row's date reflects the last actual verification, not a mass timestamp. Corrections are welcome - open an issue with the source URL and the row will be updated on the next pass.
Related content
See the React Compiler 1.0 announcement at react.dev/blog/2025/10/07/react-compiler-1 and the cross-tool installation guide at react.dev/learn/react-compiler/installation. For migration planning at scale, the annotation-mode path pairs well with codebase-wide rollouts of strict mode and React 19.