Ah, wondering how long it will take Angular to replace it's sh*t building tool chain to fully vite compatible, hope it could happen before I change may career path or retire.
Vite 8.0 Is Out
61–70 of 216 posts
Re: Vite 8.0 Is Out
#62Very pleased to see such performance improvements in the era of Electron shit and general contempt for users' computers. One of the projects I'm working on has been going for many years (since before React hooks were introduced), and I remember building it back in the day with tooling that was considered standard at the time (vanilla react-scripts, assembled around Webpack). It look maybe two minutes on a decent deve…
It is especially weird because JavaScript was not supposed to be processed at all! This is all wrong if you ask me. Web development should strive to launch unchanged sources in the browser. TypeScript also was specifically designed so engine could strip types and execute result code. These build tools should not exist in the first place.
If you're already passing over the sources to strip the types, why would you also not do tree-shaking and minifications?
Re: Vite 8.0 Is Out
#63> Currently, the Oxc transformer does not support lowering native decorators as we are waiting for the specification to progress Does Oxc also support TS runtime features like constructor parameter properties and enums? I seem to recall in the beta that they had enabled --erasableSyntaxOnly, presumably because Rolldown / Oxc didn't support doing a full transform.
Yes, those work fine: https://playground.oxc.rs/?options=%7B%22run%22%3A%7B%22lint... For that matter, TypeScript's version of decorators ("experimental decorators") also works: https://playground.oxc.rs/?options=%7B%22run%22%3A%7B%22lint... What's not supported is the current draft proposal for standardized ECMAScript decorators; if you uncheck experimentalDecorators, the decorator syntax is simply passed through as…
It doesn't support const enum, unlike esbuild which supports them well enough to be credible.
Re: Vite 8.0 Is Out
#64[flagged]
Re: Vite 8.0 Is Out
#65Earlier quoted context omitted.
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 […
Next took a very bad turn and double downed on it. Coupled with years of terrible bugs its beyond repair for me unless they rewind a bunch of core changes they did. There are several much better options right now. My favourite is Tanstack Start. No magice, great DX
+1 for Tanstack start. I just setup a new project with it and like the whole ecosystem. Only slight disadvantage is most third party documentation and automatic setup with packages aren't setup for Tanstack Start yet.
Re: Vite 8.0 Is Out
#66Earlier quoted context omitted.
It is especially weird because JavaScript was not supposed to be processed at all! This is all wrong if you ask me. Web development should strive to launch unchanged sources in the browser. TypeScript also was specifically designed so engine could strip types and execute result code. These build tools should not exist in the first place.
JavaScript was not supposed to a lot of things.
And yet it pays my bills for almost two decades.
Re: Vite 8.0 Is Out
#67Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.
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 […
Any suggestions to replace NextJS when you only use static export (no SSR)?
Re: Vite 8.0 Is Out
#68Vite 8 is pretty incredible. We saw around an 8x improvement (4m -> 30s) in our prod build, and it was nearly a drop-in replacement. Congrats (and thank you!) to the Vite team!
4 minutes?! How large is that app? Not meant as a gotcha but I'm surprised because people always tout it as being so much faster than Next. (4m with Turbo would have to be a crazy huge app IME)
Yeah, 4 mins is currently the avg. build time for our TanStack app dockerized. The turbo part takes 30 sec with Vite 7
Re: Vite 8.0 Is Out
#69Thanks to the Vite team for building a faster, modern bundling solution on a fully open source stack that isn't tied to a specific framework...cough cough, Turbopack
Re: Vite 8.0 Is Out
#70Vite 8 is pretty incredible. We saw around an 8x improvement (4m -> 30s) in our prod build, and it was nearly a drop-in replacement. Congrats (and thank you!) to the Vite team!
We saw 12m -> 2m on one of our biggest projects. Incredible really.
It blows my mind that there is a 12m build for a JavaScript application. How may lines of code is this app?