[lakomen]

Svelte Kit is great for static is "classic"-like websites.

I've converted my company website to svelte-kit from first Angular, then Vue.

But for SPA it's bad. If you use oidc auth. There's only Auth.JS and it's a confidential client, for Svelte Kit.

If you're not using svelte-kit you can use vite to create a Svelte SPA. There you can use your PCKE client as usual and burden the load on the client.

I have yet to experiment with how well it works with a graphql client. Apollo has its own cache but I'm not sure there is a svelte version of it. There is for Vue. Does it even need one? The default is for React. Is Apollo even needed? Questions over questions.

Why Svelte? Performance. Performance matters, a lot.

Svelte being a "language". First time using a template system? I have to wonder.

[wg0]

SevelteKit has some rough corners. The debugging is not as smooth especially because these frontend frameworks needlessly insists on being server side framework first for no reason specifically because server side frameworks have very strong, battle tested options ranging from Django, Flask, echo, Rails, sinatra and what not.

This makes tooling complicated and a debugging that works out of the box for both server and client side is non existent even in SvelteKit 4.

When I'm picking up SvelteKit, it's only for its routing which isn't so great either with file based arrangements, things get out of and pretty fast.

[mrklol]

you can still use your own backend for all of the business logic which is maybe easier than doing it in svelte directly.