Dominic Gannaway

We do this intentionally, if you want to mark a variable something as reactive, it must be `$state`.

> I'm getting something similar when using the class `$state` properties set by `onblurcapture` and other events. > > Stacktrace for reference:  > >...

Fixed with https://github.com/sveltejs/svelte/pull/13694

@kyle-leonhard Looks like Svelte is moving the DOM element using `element.before(target)` in the each block, and somehow that invokes `HTMLTableRowElement.target_handler`. What is that handler hooked up to event wise? It...

> > @kyle-leonhard Looks like Svelte is moving the DOM element using `element.before(target)` in the each block, and somehow that invokes `HTMLTableRowElement.target_handler`. What is that handler hooked up to event...

I put up a PR that should hopefully resolve this if merged https://github.com/sveltejs/svelte/pull/14016

> i think its still not in 5.2.10? post-poning my migrations until then. It was released a while ago. Does it still affect you on the latest version?

@m-poh You can't mutate state in a derived and we only detect it at runtime as reactivity is runtime driven. We might be able to detect some obvious cases at...

I honestly don't think we should do this – and I have a ton of experience in this field having seen how first-hand this mismatch hell caused all sorts of...

I wonder if the correct solution is that we have a better API for these cases, see https://github.com/sveltejs/svelte/issues/14337.