There should be a different rune for creating state with object arg: $proxy({value: 1})

[vjpr]

When state is given an object it compiles to a proxy object which can be passed to an external store which can read a property reactively.

When given a scalar, it cannot be passed to a store unless it is in a getter.

This is very confusing.

Is there a reason why I shouldn't just use objects for all my state so that if I need to pass them to module stores I can?

[brunnerh]

Is there a reason why I shouldn't just use objects for all my state so that if I need to pass them to module stores I can?

It is more clunky to use and passing state around should be more the exception rather than the rule, so doing that when you do not really need to does not make much sense.

I also do not think introducing a new rune improves the situation in any significant way. If you want to opt out of proxy creation, there is $state.raw.

[vjpr]

I don't want to opt out, but rather opt-in or receive error.

A state scalar behaves very differently to a proxy.

Exporting state and passing state to external modules requires reading caveats in the docs that are easy to forget.