vite-vs-next-turbo-hmr

It's the Vercel way to first run broken previews for several years. Next started with Turbopack alpha as a Webpack alternative in Next 13 (October 2022) and finally marked Turbopack as stable and default in Next 16 (October 2025). They also ran sketchy benchmarks against Vite back in 2022 [0]. Next's caching has a terrible history [1], it is demonstrably slow [2] (HN discussion [3]), RSCs had glaring security holes [4], the app router continues to confuse and relied on preview tech for years, and hosting Next outside of Vercel requires a special adapter [5]. Choosing Next.js is a liability. 0 - https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi... 1 - https://nextjs.org/blog/our-journey-with-caching 2 - https://martijnhols.nl/blog/how-much-traffic-can-a-pre-rende... 3 - https://news.ycombinator.com/item?id=43277148 4 - https://n

Note in the benchmark, it is comparing a React JSX project using @vitejs/plugin-react (Babel based) instead of @vitejs/plugin-react-swc (SWC based). I made the exact same point two years ago when Turbopack came up with a similar benchmark: https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi... The point is if we want to compare bundler performance, we should keep all the non-architectural variables consistent across all implementations. Otherwise we are not comparing apples to apples. PR submitted to update the benchmark: https://github.com/farm-fe/performance-compare/pull/11

From Evan You: > There were number rounding issues in the original numbers for the 1k component case - Turbopack's 15ms was rounded down to 0.01s while Vite's 87ms was rounded up to 0.09s. This further got marketed as a 10x advantage when the original numbers were close to 6x. I guess they 'typo-ed' Vite's numbers as well. https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi...

Another benchmark by maintainer of Vue and Vite, Evan You: https://github.com/yyx990803/vite-vs-next-turbo-hmr He seems to imply that Turbopack is very close in performance to existing tooling like Vite in his benchmark, and not 10x better in common cases Edit: his thoughts as of this hour: https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi...