Henry Lie - How does SvelteKit Fare as a SPA Framework?

[@mdriaz5334]

wow, I didn't many of them, the video maybe old, but it is great, hope to see more of them for upcomming svelte 5 releases also

[@Rhysling2]

Excellent overview. Thank you.

[@charlieroosen]

Great presentation. Thanks for sharing it.

[@phoneywheeze]

cant you declare a hooks.client.js file?

[@zBrain0]

The only problem with sveltekit is its router. It's great for small projects and I've used it for a few. It's great for something like a UI Library. But if you're writing something complicated having all of your files named the same thing becomes a nightmare very quickly. I really wish they would create an option for a declarative router within kit.

[@SvelteSociety]

There are solutions to this. If you're using VSCode you can change the way things are displayed in the tabs for example. When searching for files you should be able to just search for the route name to get all the specific files for that route as well.

[@zBrain0]

@SvelteSociety I have tried several things. At some point if you are writing a complicated app the routing just simply becomes a nightmare. For simpler projects it's a really good tool, I recently wrote a pwa using it and had a really good experience. But for some things a declarative router is just objectively better.

[@deepjyotideb1173]

@@zBrain0 nextjs also follows a similar pattern tho? Would that make it a bad choice for building complex apps?

[@zBrain0]

@@deepjyotideb1173 in my opinion yes. I have a control panel app that has literally hundreds of endpoints. Some of them are quite deeply nested. At some point it just becomes a gigantic bowl of spaghetti. I'm sure people have done it, but that doesn't mean it's a good idea.

[@fscoders]

​@@zBrain0 What i did is I make the +page.svelte just a wrapper. It will just import the component, Such as products/+page.svelte will import products/Products.svelte. So when editing or searching, i will just use Products.svelte