Post

Thilo Maier
@maier.tech

Same experience. The migration script is a great start and it's probably ok to roll with `run` for a while. But eventually you will need to do the hard work and figure out what all the reactive statements really do.

Mat Simon
@matsimon.dev

Yes, it's quite the change, but the Svelte team has done such an amazing job of allowing you to do the migration in increments. In essence, your migration is complete by changing the version number to ">5.0.0". You can just migrate each component to runes mode when it makes sense.

Noel Jacob
@handle.invalid

Just want to say you guys are unreal πŸ”₯. Just wishing it doesn't get bloated or get some obscurely used feature. Maybe try bringing in features popular in other frameworks.

Dominic Gannaway
@trueadm.dev

We hear you! Svelte 5 actually deprecates a ton of API surface area, so where we can simplify and unify APIs for the greater good, we will. Error boundaries were a key missing piece that almost every other framework has already, and there's been huge demand for them for years.

Mat Simon
@matsimon.dev

So far every change in Svelte 5 has been excellent so I'm confident it'll continue like this. In regard to error boundaries: do you have a good example on when to use it? It looks like a powerful feature but I'm not quite sure when I should actually use it.

Dominic Gannaway
@trueadm.dev

You'd likely wrap parts of your app where you might be using something that might error - like some third party service in an effect. Then you can show that an error happened without the whole app failing and the user needing to refresh the page.

Mihin Dissanayake
@mihinmud.bsky.social

This is great but I actually miss the challenges and puzzles from the previous advent of svelte. I am actually trying to use svelte as a part of the advent of code challenges for this year. Maybe like a ui/frontend for the elves to use?

Mihin Dissanayake
@mihinmud.bsky.social

True, but I actually did use Svelte 5 during that time even though it was in beta. I am not complaining these features do look really awesome! More than enough to make up for the puzzles. πŸ™‚

Adam Rackis
@adamrackis.bsky.social

Still no way to add state? React community discovered long ago that stateless components have very limited utility. The constant conversion from SFC to classes led many to just forgo the former altogether.

Mat Simon
@matsimon.dev

That's really cool, and I'm sure there are use cases where this will be extremely convenient. But out of the box I find it hard to find an actual use case for it. The demo seems to be a bit of an antipattern (I could achieve the same with simple components). Do you maybe have a real world example?