svelte-error-boundary VS carbon-components-svelte

Apparently it's quite a complex problem from what I have gathered. While there are packages like @crownframework/svelte-error-boundary that can guard from initialization-time errors, which I have blogged about, they sometimes don't work with asynchronous errors or errors triggered in child components. So it would actually be huge to have built-in support for error boundaries.

I agree with you error boundaries are a huge omission. You can do basic error boundaries using one of these two packages:

* https://github.com/crownframework/svelte-error-boundary

Thankfully there is a community package available that implements error boundaries! 🤩

We did a pretty big one, integrated with a python/gtk app [yikes]. Anyways, svelte is a joy to work with, also on the note of libraries, svelte's community is smaller but I found by far my favourite component system I've ever used - https://carbon-components-svelte.onrender.com/.. surprising coming from IBM, but hey, I'll take it.

But in general electron was a pain, slow builds - had an adhoc solution for the svelte dev server, but its not great.

https://carbon-components-svelte.onrender.com/ maybe this is something for you.

I really liked Carbon Components Svelte but they lacked mobile support. I will have to check Framework7 .

If you need something with a bit more functionality out of the box, I'd recommend -Carbon Components (https://carbon-components-svelte.onrender.com) -Skeleton(https://www.skeleton.dev)

Svelte/SvelteKit does have some high-quality libraries available like carbon-components-svelte but there's just nothing near as much.

I've opened issue on IBM community to find a solution rather than importing via , although I could not even get any answer to that . After sometime of scratching my head and couple of tests on Webpack behaviour, I've managed to crack carbon-design-system for Svelte once and for all . Repeating myself:

You could check out Carbon https://carbon-components-svelte.onrender.com/