Warning: Properties of objects and arrays are not reactive unless in runes mode

[MrWaip]

Describe the bug

Hi, I just updated svelte to version 5, and I get this warning

Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update 

There is obviously some bug in the analyzer. I do not mutate the object, but read its property

Reproduction

https://svelte.dev/playground/d38ff4e52c9c4b1cb7b5314a662e479a?version=5.0.5

Logs

No response

System Info

svelte@5.0.5

Severity

annoyance

[MrWaip]

This is also reproduced with typescript enams

[brunnerh]

There is obviously some bug in the analyzer. I do not mutate the object, but read its property

The warning is telling you that if Marker.A is changed elsewhere, this reactive statement will not trigger in legacy mode.
The warning is correct in principle, but if Marker.A is immutable, this is a false positive.

You can ignore the warning using

// svelte-ignore reactive_declaration_non_reactive_property

[MrWaip]

In my case Marker is immutable. It's enum.

I don't really like the idea of monkey patching everywhere with comments)

[brunnerh]

The problem is probably that components are analyzed in isolation, possibly without type information from the outside; at least that used to be the case previously.

[paoloricciuti]

The problem is probably that components are analyzed in isolation, possibly without type information from the outside; at least that used to be the case previously.

Yup this is correct

[MrWaip]

Tricky rule

[benmccann]

here's a Svelte 5 upgrade PR that has lots of ignores related to this warning if you want to see some examples: immich-app/immich#13738