Post

🎅🎄🎁 ADVENT OF SVELTE 🎅🎄🎁 We're going to ship one thing a day every day from now until Christmas. Wish us luck! svelte.dev/blog/advent-... First up...

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.

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.

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.

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.