Only folks who help package Chromium get to decide how Chromium gets packaged. This gives anyone two options: You can get involved and help package Chromium so you have a voice in the decision-making, or not.

Yet another comment with why is this not implemented is not helpful for devs.

I had this problem and figured out how to make something like this work with the compiler quirks.

Svelte should make something like useEffect part of the framework so that this could work better and be less verbose.

I’d still be interested in Svelte making things easier so I’ve opened a feature request for Reactive statement cleanup functions.

If you can't understand where it's coming from in the stack traces, please post screenshots or create reproducing sandboxes and we'll try to help. Most of these are probably coming from a few libraries, so the most productive thing to do is to reduce these cases and then file issues with those libraries.