svelte-query VS svelte-spa-router

Nice I was waiting for this! I'm using the old implementation: https://sveltequery.vercel.app/

I'm aware there's another Svelte Query here but it seems like it is not maintained and will be incorporated into Tanstack Query.

Until then I use Svelte Query

I like React Query so I would be excited to use this however it doesn't seem ready for Svelte given the docs "Coming Soon" and Svelte Query being relatively unmaintained.

Svelte Query :)

Or just use svelte-query and toss that observable junk to the side.

Exactly. That's the big thing I want to work on next. Not sure whether to use Svelte Query or manually cache the data. In an ideal scenario all the API calls are cached because if two users hit the site at the same time, for instance, there's no need to request the same data twice. This is getting to the edge of my skillset but psyched to try to learn this part.

That's it. Nothing highly sophisticated. It is mostly the tech I enjoy and I think is valuable in the future. There are also other libraries I really enjoy, like XState and React Query (there is also Svelte Query). Just to mention a few.

Caching: svelte-query, sswr

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