svelte-starter-kit VS svelte-spa-router

I started adding Typescript to my project. I found Svelte-Starter-Kit is useful.

You can check how it's done in Svelte Starter Kit

I love Supabase, and maintain a SvelteKit + Supabase Open-Source Starter Kit, but between Supabase and Headless CMS, for this use case, I'd definitely recommend a Headless CMS. Any headless CMS(including WordPress) you prefer.

If you want to use the load function on the server, you'd be required to maintain the JWT token in a cookie, access it on the server in an API route/endpoint, and then you'll have to make calls to those API endpoints in the load function to check a user's credentials. Something like Svelte Starter Kit's Profile Page.

It's fixed now https://github.com/one-aalam/svelte-starter-kit/issues/17

Head over to https://github.com/one-aalam/svelte-starter-kit/tree/auth-supabase to explore! (More exciting updates on the way)

Hey, you can see how it's done here

3 things to comment here. The first is the use of the svelte-spa-router library (for more details see its doc here). For the simple purpose of changing views in a desktop application, this library more than fulfills its purpose. With the 7 views or pages we create a dictionary (or JavaScript object) that associates routes with views. Then this dictionary is passed as props to the Router component of svelte-spa-router. It's that simple. As we will see later, through programmatic navigation or through user action we can easily change views.

But the choice depends on the type of application though. If your routes are not dynamic (not using variables within route) then you can use static site generation (SSG) which will generate the various html files. Otherwise you need to use the same file (index.html#my/dynamic/route/5). To my knowledge svelteKit doesn't support hash-based routes. You might be able to configure routing without it, but if you need that, you me be better off to use svelte with svelte-spa-router and not sveltekit.

https://github.com/ItalyPaleAle/svelte-spa-router seems good too.

but it's not official, and Svelte project seems careless for client routing, instead it tries to convince everyone use its SSR-first kit, that "can do CSR too", which means you have to carry the whole SSR code base and its documentation into your CSR project totally unnecessarily.

I get it Vercel needs SSR for its business, I don't get it why it keeps selling everyone that "my SSR-first framework is great for CSR SPA too", it is NOT, not at all.

For a simple static site you can just use svelte with svelte-spa-router. If you want SSG, use Astro, it's a lot more mature than SvelteKit.

Svelte SPA Router - You need a router. NextJS, which you have experienced in, comes with a router.

Svelte SPA Router

I am using Keycloak for logging into my app and svelte-spa-router for hash based routing inside my SPA. After successful login, Keycloak should redirect back to http://localhost:1234/#/myRoute . However, Keycloak appends some suffixes to this route. The route ends up looking something like this: http://localhost:1234/#/myRoute&state=hexstring&session_state=hexstring... etc As I defined my route (inside routes.js) as /myRoute , the router fails to parse the URL returned by keycloak. Looking at the source code I noticed that keycloak changes the URL back to the "clean" parameterless URL: http://localhost:1234/#/myRoute using a call to window.location.replaceState . Unfortunately, this call does not get reflected in the spa-routers internal svelte store (i.e. $location).