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
Re:Vite 8.0 Is Out
by adamgoodapp on Friday March 13, 2026 @05:14AM
(#47362151)
+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
by littlecranky67 on Friday March 13, 2026 @05:19AM
(#47362185)
Any suggestions to replace NextJS when you only use static export (no SSR)?
Tanstack Start is the gold standard here. It’ll do a static export no problem.
Astro: https://astro.build/
Re:Vite 8.0 Is Out
by littlecranky67 on Friday March 13, 2026 @07:59AM
(#47363246)
From my first glance, it is not really. Has its own templating syntax, its own file format etc. With NextJS static export I only have valid react/tsx and would not want to introduce a framework-specific language. Also could not easily find something about the routing
While Astro does indeed have its own type of components, it also supports React, Solid and a host of others. So transplanting your current tree of components in, adding the React plugin and saying "GO" is likely a fairly straight-forward project. I moved a previous static site into an older verison of Astro with very little trouble.
Re:Vite 8.0 Is Out
by christophilus on Friday March 13, 2026 @05:42AM
(#47362335)
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
by littlecranky67 on Friday March 13, 2026 @08:02AM
(#47363287)
Care to list those?
Re:Vite 8.0 Is Out
by NamlchakKhandro on Friday March 13, 2026 @05:46AM
(#47362357)
tanstack router
Re:Vite 8.0 Is Out
by BoorishBears on Friday March 13, 2026 @12:02PM
(#47366249)
I'm surprised anyone's using Next for static exports when they've left dynamic paths broken for years.
I recently migrated to Tanstack for this and confirm it's been strictly better so far, especially having dynamic paths in my use-case (makes a hybrid app much more realistic)
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://nextjs.org/blog/CVE-2025-66478
5 - https://opennext.js.org/