svelte-spa-router VS routify

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).

How does Routify compare with svelte-spa-router[1]? I really like svelte-spa-router for a simple SPA, though I think a lot of SPA routers don't always handle state well.

[1] https://github.com/ItalyPaleAle/svelte-spa-router

Been using Routify in all my projects since I started with Svelte like 3-4 years ago.

Anyway, it seems you have a problem with Sveltekit routing. You can still use Svelte with other SSR frameworks, such as Astro, a router like https://routify.dev, or switch to another framework altogether.

Routify is still active and new version in the works. Version 3 can be used https://github.com/roxiness/routify/tree/next

I would have to say Svelte with a router like https://routify.dev . My recent blog post originally used sveltekit but I swapped it out last minute

Consider https://github.com/roxiness/routify

Regarding some suggestions on here recommending SvelteKit: Learning SvelteKit might be a big ask depending on what you're trying to do. If you just want to stick with svelte only for now, and you want to add SPA routing capabilities, consider checking out https://routify.dev there's a ton of documentation for it and it's fairly simple to pick up. ✌🏼

Routing: We have a few third party ones such as routify, svelte-spa-router and svelte-routing as well as the clientside routers included in SvelteKit and Sapper.

if Next.js/Nuxt like needs are not something you're looking for yet, you can definitely go ahead with Svelte's default client-side app approach, with svelte-spa-router or routify for SPAs.

We chose Routify for client-side routing because this was around the time that Sapper seemed like it was being sunset in favor of Sveltekit which doesn't seem production-ready quite yet. We also have plans to statically pre-render the app so it can more-or-less work entirely offline and Routify makes that relatively straightforward (but see below).

Since svelte does a lot of compile time stuff, I would like to mention Routify, which is compile time SPA routing. For me it worked awesome to accomplish projects with many routes and the need for hash based routing.

See https://routify.dev/ and https://routify.dev/guide/installation/install-to-existing-p...