Babel has had its day
Babel has been around since 2014, back then under the name 6to5. It compiles modern JavaScript and TypeScript into code every browser understands, and it is written in JavaScript itself. Today Oxc does the same job, written in Rust.
Vite 8 sets the direction.
It bundles with Rolldown, compiles with Oxc, and the React plugin for Vite removed Babel completely in version 6.0.0.
The changelog puts it plainly:
Vite 8+ can handle React Refresh Transform by Oxc and doesn’t need Babel for it.
Babel is still maintained, version 8 is current. Even so, it no longer belongs in the build path of a Vite project.
What Oxc brings
The Oxc team benchmarks itself publicly against Babel and SWC, in the repo bench-transformer on GitHub Actions runners:
- 20 to 50 times faster at compiling TypeScript and JSX.
- 20 to 70 times faster in React development mode with React Refresh, which is exactly what the dev server does for every file.
- Less memory: 57 MB instead of 180 MB when compiling the same file.
- 2 packages instead of 170 on install.
Benchmarks
Vendor numbers are one thing. So I set up my game halma twice, once in its previous state with Vite 7.3.7 and plugin-react 5.2.0, once with Vite 8.3.4 and plugin-react 6.1.2. Measured on an Intel Core i7-14700 with Node 24.15, median in each case.
| before | now | factor | |
|---|---|---|---|
| Compiling the 22 source files (3,738 lines) | 72.6 ms (Babel 8.0.7) | 2.7 ms (Oxc 0.154.0) | 27 |
| Dev server, cold start until the page has loaded | 1,489 ms | 747 ms | 2.0 |
vite build |
4,007 ms | 3,123 ms | 1.3 |
For compiling, both got the same job: strip TypeScript, JSX in development mode and React Refresh.
A spot check on App.tsx shows equivalent output, both have the same JSX calls and the same Refresh registration.
The factor of 27 sits right in the middle of the range the Oxc team states.
The other two rows measure Vite 8 as a whole, including the new bundler.
For everyday work they are the more important numbers:
The dev server is up in half the time, and that on a small project with 22 files.
Happy Watches.de: Babel as dead weight
Happy Watches, my directory of Swatch Chrono models, still had Babel on board as well. The site runs on Astro 7, but the React integration was still on 4.4.2. It pulled in plugin-react 4.7.0 with Babel, plus a second Vite in version 6.
Babel never compiled anything there. The site has not a single React component. It just sat in the project.
An update to @astrojs/react 7.1.0 cleaned up:
- Packages in the lockfile: 337 instead of 440
- Babel packages: 4 instead of 22
- Vite: only version 8.3.4, the second Vite is gone
Astro itself brings the four remaining Babel packages, @babel/parser via the helper package magicast.
So Babel does not disappear entirely.
What matters is that it no longer touches any file that is built or served by the dev server.
How to get rid of Babel
npm ls @babel/core shows who pulls in Babel.
If it lists @vitejs/plugin-react in version 4 or 5, the way out is short:
- Vite project: raise
viteto 8 and@vitejs/plugin-reactto 6. - Astro project: raise
@astrojs/reactto 7, Vite 8 comes along automatically. - Your own Babel plugins, such as the React Compiler: they only run through
@rolldown/plugin-babel, which you add explicitly. For the React Compiler there is also a Rust version,oxc-transform-react, 12 to 16 times faster according to bench-transformer.
But watch out:
With halma, npm install stopped with a conflict (ERESOLVE).
The PWA plugin brings @babel/core version 7 via workbox, while the new React plugin points to Babel 8 through an optional peer.
With --legacy-peer-deps the install went through, and afterwards the site worked without a single console error.
Babel stays in the lockfile there too, because workbox and the ESLint plugin for React Hooks need it.
It is out of the build path all the same.
Time to look ahead
Babel has done its job. Many tools of the JavaScript world are being rewritten in Rust right now, and Vite has made its choice. Anyone still on Vite 7 or an old React integration loses time on every dev server start. A look at your own lockfile is all it takes. For Happy Watches the switch was a single version bump, for halma it was three packages.
Sources (checked on October 17, 2026): Oxc · Oxc, bench-transformer · plugin-react, changelog 6.0.0 · plugin-react, pull request #1123 · Babel · Babel, renaming from 6to5 · halma