Yeah, I've done the no-JS capable thing for a vanilla Svelte app with an express backend on EC2. Required a bit of bushwhacking to get the svelte routing working on the server, but worked really well in the end.
I think Sveltekit makes this easier, but at the cost of being more complex to self-host (you might get tied to Vercel which employs Rich Harris and makes all the Sveltekit SSR stuff "just work" in ways that I'm concerned won't just work if you're not using vercel)
The Vercel adapter may get some more attention and features first (like ISR[1]), but local development only requires NodeJS. So I think you can self-host SvelteKit anywhere that supports NodeJS. SvelteKit is designed to be serverless-first, but still supports traditional servers-based deploys.
And there are several non-Vercel adapters that should just work (Node, Cloudflare Pages, Cloudflare Workers, Netlify, static site generation)[2].
Comments
Yeah, I've done the no-JS capable thing for a vanilla Svelte app with an express backend on EC2. Required a bit of bushwhacking to get the svelte routing working on the server, but worked really well in the end.
I think Sveltekit makes this easier, but at the cost of being more complex to self-host (you might get tied to Vercel which employs Rich Harris and makes all the Sveltekit SSR stuff "just work" in ways that I'm concerned won't just work if you're not using vercel)
The Vercel adapter may get some more attention and features first (like ISR[1]), but local development only requires NodeJS. So I think you can self-host SvelteKit anywhere that supports NodeJS. SvelteKit is designed to be serverless-first, but still supports traditional servers-based deploys.
And there are several non-Vercel adapters that should just work (Node, Cloudflare Pages, Cloudflare Workers, Netlify, static site generation)[2].
And even more unofficial adapters[3]!
[1]: https://kit.svelte.dev/docs/adapter-vercel#incremental-stati...
[2]: https://kit.svelte.dev/docs/adapters
[3]: https://sveltesociety.dev/components#adapters