Vite 8.0 Is Out • Hacker News Board

Re: Vite 8.0 Is Out

#71

Post by christophilus » Fri, Mar 13, 2026, 9:42 AM UTC

littlecranky67 wrote: post #67

gherkinnn wrote: post #26

Earlier 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 […

Any suggestions to replace NextJS when you only use static export (no SSR)?

It depends on your application, but for typical SPAs, there are any number of approaches which are better than next by every metric I (personally) care about.

Re: Vite 8.0 Is Out

#72

Post by rozenmd » Fri, Mar 13, 2026, 9:42 AM UTC

vijaybritto wrote: post #16

rvcdbn wrote: post #11

Earlier quoted context omitted.

maybe of interest: https://github.com/cloudflare/vinext (haven't tried it myself)

It's not a good piece of software. Breaks in many places

that makes sense, it's not 1.0 yet

Re: Vite 8.0 Is Out

#73

Post by wiseowise » Fri, Mar 13, 2026, 9:43 AM UTC

pjmlp wrote: post #43

wiseowise wrote: post #32

Earlier quoted context omitted.

It takes tooling team and discipline to keep compile times at bay when you reach mid size projects with compiled languages (looking at you Java, C++, Rust).

Lack of discipline is exactly the magic word regardig the node ecosystem mess.

Maybe? The point still stands that majority of programmers/industry is not equipped to deal with this adequately.

Re: Vite 8.0 Is Out

#74

Post by christophilus » Fri, Mar 13, 2026, 9:46 AM UTC

Griffinsauce wrote: post #35

flowerbreeze wrote: post #28

Earlier quoted context omitted.

I'm being rather snarky here, but the main point of front-end JS UI frameworks is to exist and to survive in their environment. For this purpose they have evolved to form a parasymbiotic relationship with others in their environment, for example with influencers. The frameworks with the best influencers win out over older ones that do not have the novelty value anymore and fail to attract the best influencers.

This could also apply to the recent wave of hate towards Next.

Next is the Microsoft Sharepoint of the JavaScript world. It’s a terrible solution to just about anything, and yet gets crammed into places and forced on people due to marketing-led decision making.

Re: Vite 8.0 Is Out

#75

Post by NamlchakKhandro » Fri, Mar 13, 2026, 9:46 AM UTC

littlecranky67 wrote: post #67

gherkinnn wrote: post #26

Earlier 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 […

Any suggestions to replace NextJS when you only use static export (no SSR)?

tanstack router

Re: Vite 8.0 Is Out

#76

Post by throwaway290 » Fri, Mar 13, 2026, 9:51 AM UTC

Outsider question: why use Rollup when Esbuild exist? Is esbuild not enough for production builds?

Re: Vite 8.0 Is Out

#77

Post by ZiiS » Fri, Mar 13, 2026, 9:52 AM UTC

olmo23 wrote: post #62

vbezhenar wrote: post #53

Earlier 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.

If you're already passing over the sources to strip the types, why would you also not do tree-shaking and minifications?

Why would I want to strip my types?

Re: Vite 8.0 Is Out

#78

Post by christophilus » Fri, Mar 13, 2026, 9:58 AM UTC

wiseowise wrote: post #32

pjmlp wrote: post #20

Earlier quoted context omitted.

Why go halfway, embrace compiled languages in the backend. Fast all the way down, especially when coupled with REPL tooling.

It takes tooling team and discipline to keep compile times at bay when you reach mid size projects with compiled languages (looking at you Java, C++, Rust).

But, it doesn’t need to be so. Go is pretty fast to compile. So is Jai, from what I’ve seen. So was TurboPascal. Rust has a similar problem to the one Vite has been solving- Rust (and most languages) weren’t designed for compilation speed, and it’s hard to retroactively fix that. But, there’s no reason we shouldn’t have a bunch of statically typed, fast-to-compile languages.

Re: Vite 8.0 Is Out

#79

Post by h4ch1 » Fri, Mar 13, 2026, 10:04 AM UTC

I've been using rolldown-vite for the past 3-4 months with absolutely no issues on a very large monorepo with SvelteKit, multiple TS services and custom packages.

Just upgraded to 8 with some version bumping. Dev server time reduced to 1.5s from 8s and build reduced to 35s from 2m30. Really really impressed.

Re: Vite 8.0 Is Out

#80

Post by raydenvm » Fri, Mar 13, 2026, 10:05 AM UTC

Yeah, it makes you wonder how much computing power the industry has wasted over the years on tools that nobody questioned because "that's just how long builds take." We planned our work around it, joked about creating breaks, and built entire caching layers to work around it.

Kudos to the Vite maintainers!