3 ms·
Any suggestions to replace NextJS when you only use static export (no SSR)?
by littlecranky67 8mo ago
Any suggestions to replace NextJS when you only use static export (no SSR)?
- christophilus 8mo agoIt 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.
- littlecranky67 8mo agoCare to list those?
- NamlchakKhandro 8mo agotanstack router
- dbbk 8mo agoTanstack Start is the gold standard here. It’ll do a static export no problem.
- J_tt 8mo agoAstro: https://astro.build/ https://astro.build/
- littlecranky67 8mo agoFrom 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
- nobleach 8mo agoWhile 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.
- BoorishBears 8mo agoI'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)