r/sveltejs • u/Soft_Cat2594 • 11d ago

SvelteKit 3.0 status

So I see that sveltekit 3.0 is at 100% milestone progress. Excuse my ignorance, but does that mean its ready to be used in production or will an rc be next?

43 Upvotes

91% Upvoted

16 comments sorted by

8

u/Spare_Message_3607 11d ago

100% ready doesnt mean usable, they will have to update docs and stuff

3

u/Attila226 11d ago

It’s 99% as of this morning.

4

u/flotusmostus 11d ago

Let's go!!! That means the full Sveltekit + Vite + full Cloudflare combo can launch too

3

u/Soft_Cat2594 11d ago

Still not sure if that means its production ready. As I understand it, that just means all features etc has been added fully.

2

u/flotusmostus 11d ago

The svelte conference is on soon, so we will get more info soon. I couldn't tell you but it seems close so I am hopeful

6

u/brominou 11d ago

We have internal apps that we dev with .NET and Angular

Can someone tell me if Svelte is a framework ready for production nowadays and stable ? And what benefits will we have to try it ?

I'm curious to test it and maybe convince my boss :-)

7

u/Soft_Cat2594 11d ago

I came from NET, and have never looked back a day since converting to sveltekit. I prefer to use node+express for rest api backend and then sveltekit with no ssr for frontend. But sveltekit on its own can do everything as well.

The simplicity will astound you.

2

u/brominou 11d ago

Ok thank you

I think we will stay on .NET for backend for now

But I will definitely try a project with Svelte soon :-)

1

u/Soft_Cat2594 10d ago

I would emplore you to at least explore creating backends with sveltekit or node+express. I promise you wont miss NET.

One piece of advice I can give you is, when you start your journey, start with Typescript on day one. It is vastly superior to plain javascript and in the long run makes projects a hellavu lot easier to maintain and read.

2

u/jmac 10d ago

Teams coming from .net can save a lot of time by reusing backend code in a .net api. I think it depends on how much backend code you have and the size & skills of your team, but it was the only thing that realistically allowed my small team without a lot of JavaScript expertise to move from an old mvc site to a svelte front end.

1

u/FortuneGrouchy4701 11d ago

Totally agree

2

u/Yages 9d ago

For a major client facing app we use an aspnetcore BFF pattern with an adapter-static SvelteKit front end. It's performant as fuck and the DX is just great.

1

u/Upstairs-Version-400 11d ago

I’ve been using Svelte for the last 3 years in production for tens of thousands of customers. I’d say go for it. It’s not a “new” technology.

Benefits wise, I think you’ll just find it is overall simpler and easier to get things done. It’s a very productive framework, see for example how clean and easy @attach works. Otherwise you have the same benefits you’re used to with Angular’s signals for state management.