SvelteKit's routing pattern is anything but clean. It uses filesystem based routes where every file is called "+page.svelte" (or +page.server.js/ts for API only routes).
For anything but a demo app with just a couple of routes it's a headache to navigate.
Edit: Another smell of the routing system to me is that you need to resort to complexity like this [1] to have anything but top down inheritance. I love Svelte btw and have used it in many projects.
For anything but a demo app with just a couple of routes it's a headache to navigate.
Edit: Another smell of the routing system to me is that you need to resort to complexity like this [1] to have anything but top down inheritance. I love Svelte btw and have used it in many projects.
[1] https://kit.svelte.dev/docs/advanced-routing#advanced-layout...