Dominic Gannaway

@minht11 This is to be expected. If you change the button to be `on:click` it will attach directly to the element without delegation and that should work.

I mean if you think of it properly, destructuring properies is a form of reading a derived value. So it makes sense why it would need be to wrapped with...

> Oops, I didn't know that destructuring an object would lose reactivity. What's funny is that I use only stores with array $state, and in this case, destructuring doesn't cause...

There's not much we can do about this. We can list this as a breaking change, but the event object is shared along the listeners to improve performance. I thought...

@brunnerh Event delegation has a significant impact on performance in real world applications. React has an `event. persist()` that will generate a static event object. We could do something the...

@madacol Yes, as I mentioned above, this is to be expected when using `onclick` in Svelte 5. We're doing our own event delegation for improved memory/performance (like many other frameworks...

This is to be expected. Runes are designed to read dependencies sync only – and given the browser has no native way to track async context (yet), this isn't possible...

@valterkraemer What if you call a function from a random npm module? The compiler is limited in context.

@valterkraemer That would break far too many cases as we now use runtime reactivity rather than compile time reactivity.

You can use a class to handle external state and trigger `invalidate` on it to do as you want: ```js class External { #data; #version = $state(0); constructor(data) { this.#data...