Svelte error/isolation/resilience model for components?

[Baxterboom]

I do not understand the "error model" of svelte. Runtime error in one component causes whole app to stop responding. Only way out of it is to reload (f5) the browser. This does not feel resilient to me. IMO only the affected component should fail. Am I thinking about it wrongly, or missed something in the docs about this?

Here is a example demonstrating the case.
https://svelte.dev/repl/f097db80392243ab8edc8a8d6a355e98?version=3.35.0

[dummdidumm]

What you seem to be looking for are error boundaries. There is an open rfc for it sveltejs/rfcs#46 .
Duplicate of #1096

[Baxterboom]

Are their any onboarding guides for this project? Not that straight forward how to add/contribute.

Added rudimentary onError event lifecycle to prevent app from locking up, if anyone is interested. Baxterboom#1

`<script lang="ts">
import {onError} from 'svelte';

onError(e => {
    console.warn("onError", e);
    return true;
});

</script>`