React 19 and the React Compiler: Faster Apps With Less Code

React is the library behind a large share of modern websites and web apps. It decides how screens are built and updated as people click and type. The React team has shipped a steady stream of changes since React 19 in December 2024, and the latest is React 19.3 from 9 September 2026. This post separates what is useful from what is only interesting to developers.

The timeline in one paragraph

React 19 launched on 5 December 2024. React 19.2 followed on 1 October 2025 with a component called Activity and a hook named useEffectEvent. React Compiler 1.0, its first stable version, was announced on 7 October 2025. React 19.3 arrived on 9 September 2026. On 24 February 2026 the React Foundation was launched under the Linux Foundation, which moves the project's home away from a single company.

What React Compiler does

Apps feel slow when the screen redraws more than it needs to. Developers used to prevent this by hand, writing extra wrapper code known as memoisation, which means remembering a result so it is not recalculated. The React Compiler does that remembering automatically when the app is built.

The official 1.0 announcement says it was tested on major apps at Meta and is production-ready. Meta reported initial loads and page-to-page navigation improving by up to 12 per cent, and some interactions running more than two and a half times faster. Those are figures from Meta's own apps; a small business dashboard will see something different, often a smaller gain.

Two practical notes from the same post matter to anyone commissioning work:

• The compiler works with React 17 and up. On React 17 or 18 it needs a small extra runtime package and a setting, so you do not have to be on React 19 to try it.
• It can expose hidden bugs in code that breaks React's rules. The team advises pinning an exact version and having good test coverage before upgrading it.

What is new in React 19.3

• View Transitions are stable. They animate elements as a screen changes, using the browser's own animation feature. Only updates marked as transitions animate, so ordinary typing stays instant. We explain the browser side in our post on the View Transitions API.
• Fragment Refs let code manage a group of page elements without adding an extra wrapper element. This is a tidy-up for developers more than a visible feature.
• A browser-only switch lets a component skip server rendering when it truly depends on the browser.
• Trusted Types support helps sites with strict security policies, because React no longer converts values in a way that blocks them.

Most of these will not change what a customer sees on day one. They reduce workarounds in the code, which lowers the cost of later changes.

A security fact worth knowing

In December 2025 the React team disclosed a critical vulnerability in React Server Components, followed by two more. Fixes shipped in versions 19.0.1, 19.1.2 and 19.2.1. This affects apps that use that server feature, not every React site. If a studio built your app with a framework that uses Server Components, ask which React version it runs and whether the patches are applied. Our post on supply-chain attacks covers the wider habit of keeping dependencies updated.

Should your business app upgrade?

Our own site runs React 18 as a static site, and we have not needed to move it for any visitor-facing reason. That is a fair answer for many sites. Upgrade when one of these is true:

1. The app is slow in ways users complain about, and the cause is unnecessary redrawing.
2. A library you depend on has dropped React 18 support.
3. Your app uses React Server Components and needs the security patches.
4. You plan a redesign and want animated page changes without extra libraries.

If none applies, you can stay on React 18 and plan the move for the next major piece of work, when testing is already budgeted.

How to approach the move safely

First, list what depends on React: your component library, form tools, payment widgets and charts. Second, read the React 19 upgrade guide with your developer. Third, upgrade React on its own, without the compiler. Fourth, switch the compiler on for one section of the app, measure it, and widen from there. Keep a rollback ready. This staged approach is how VS Tech Builders handles framework upgrades, because it keeps each step small enough to test properly.

The decision belongs with someone who can see your code. If you are weighing it against a rebuild, our website redesign guide and SaaS web application service page set out the options, and you can ask us for an opinion on a specific app. For the framework side of the story, read what is new in Next.js 16.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• React 19.3 — React
• React Compiler v1.0 — React
• React Blog — React

Frequently asked questions

Do I need React 19 to use the React Compiler?

No. The compiler works with React 17 and later. On React 17 or 18 it needs a minimum-target setting and a small runtime package, while React 19 needs no extra setup. Your developer should still test carefully, because the compiler can reveal hidden bugs in code that breaks React's rules.

Will React 19 make my website faster for visitors?

Not automatically. React 19 and the compiler can cut unnecessary redrawing, which helps interactive apps with heavy screens. A simple brochure site is usually limited by images, scripts and hosting instead. Measure your current speed first, then decide whether a React upgrade is the right fix.

Is React still safe to build a business app on?

Yes, with normal care. It is widely used, maintained under the React Foundation within the Linux Foundation, and security issues are patched openly. Keep dependencies updated, apply security releases promptly, and ask your developer to check advisories whenever one is published.