Rust React Compiler Lands in Vite, Babel Finally Exits the Picture
The Rust-based React compiler is now native in Vite, removing Babel from the compilation pipeline entirely for Vite users. The thread celebrates this as a meaningful performance win and notes the odd inconsistency that Next.js still requires a Babel plugin for the React compiler despite running SWC. The question 'why does Next.js need Babel when Vite doesn't?' does not have a satisfying answer in the thread.
This matters beyond the performance numbers. Babel has been a performance anchor in JS tooling for years and its removal from a major path is a signal that the Rust-in-JS-tooling wave (SWC, Vite, Biome, Turbopack) is past the early adopter phase and into mainstream defaults.
The Next.js inconsistency is worth watching. If Vercel does not close this gap, it becomes a talking point for the growing contingent of developers moving projects away from Next.js toward Vite-based stacks.
So what?
If you are starting a new React project today, the Vite path now has materially better toolchain ergonomics than Next.js for many use cases. For founders evaluating framework choices, the tooling gap is narrowing fast and the lock-in cost of Next.js is worth pricing in explicitly.