Have you tried a file based routing framework that isn’t Next?
Asking for a friend
9 comments
I've been a big fan of this engine with a radical file based routing approach that's almost entirely automatic and transparent. You can add "rewrite rules", but 99% of the time routing takes care of itself.
Highly recommend nginx
Highly recommend nginx
4d|
Anonymous
||Can’t tell if it’s a joke
4d|
Anonymous
||They're not wrong though...
1d|
Anonymous
||Try Bun, it has a file based router already included.
4d|
Anonymous
||if you want something similarly 'full fat' -- i.e includes options for both server rendered markup and client side reactivity and api routes etc then sveltekit is my goto. the ecosystem is great and very nearly as good as react imo (see https://github.com/TheComputerM/awesome-svelte for a list) and I really like the direction they're going with svelte 5 and runes.
Main downside is LLM generated code often gets confused between the major syntax differences in svelte 5 which can be annoying if you rely on that a lot (I only use LLMs for small things and don't have a problem working with svelte 5 this way)
The biggest improvement over next is just the speed, its as fast as any HTMX/php/'old school' solution and I really don't think its that much more complex either, so I don't really see why people keep insisting on using those things for proper web apps when they make it so difficult to write apps.
If you are just trying to make a simple static website though and don't need api routes then my pick would be Astro. Basically if I ever think that what I'm working on will want some form of 'context' that spans multiple pages I pick sveltekit, otherwise Astro.
Main downside is LLM generated code often gets confused between the major syntax differences in svelte 5 which can be annoying if you rely on that a lot (I only use LLMs for small things and don't have a problem working with svelte 5 this way)
The biggest improvement over next is just the speed, its as fast as any HTMX/php/'old school' solution and I really don't think its that much more complex either, so I don't really see why people keep insisting on using those things for proper web apps when they make it so difficult to write apps.
If you are just trying to make a simple static website though and don't need api routes then my pick would be Astro. Basically if I ever think that what I'm working on will want some form of 'context' that spans multiple pages I pick sveltekit, otherwise Astro.
4d|
Anonymous
||3d|
sam!f43d612d8e
||Elysia is my go to for this, if the project is more robust. For quick projects then hono with the file-based router.
2d|
Anonymous
||yes for more than 20 years, HTML in directories
7h|
Anonymous
||Symfony and a bunch of other PHP frameworks does this. After a while and scale, it becomes a bit too implicit. These days, I try to do everything explicit and referentially transparent.
6h|
Anonymous
||Add a comment