I've been using Svelte in production without SvelteKit for around 5 years now. The docs have always been pretty great in my opinion

Is there any reason you wouldn't want to use SvelteKit now that is has reached version 1.0?

The business apps I work on don't benefit from SSR (having to write components that can render server-side is friction without payoff), and I already have a client-side router that supports nesting.

What router are you using? One in the svelte ecosystem or a vanilla js router?

Also in the process of writing an app that has no ssr needs. There are some minor annoyances with SvelteKit and interested in other options.

I'm still using https://github.com/TehShrike/abstract-state-router which I wrote years ago after thinking "ui-router is great, but I need a version that can keep using no matter what component library I want to use in the future"

Yes, because Kit won't work on my target platforms.

They've been focusing on SvelteKit, so plain Svelte has stayed pretty much the same for a while. It's nice, stable, feels finished. I'm ever so slightly afraid of what could happen now attention appears to be on it again.

The docs + tutorial are very good, even approaching "fun" (YMMV).

Yep, but slowly converting it all over to SvelteKit. Saves me having to maintain servers, watch setups, build processes, deployment processes, routing, bundling, and so on.

iep, doing csr microfrontends