Reactivity Breaks When Using $state in Both a Function and a Svelte Component

[signalize]

Describe the bug

When defining a function in a .svelte.ts file that creates and returns a $state object, everything works as expected when using the function in a .svelte file. However, if the same .svelte file contains another $state definition, the reactivity of the $state object from the function breaks.

Reproduction

See the following branch to test:
https://github.com/signalize/svelte-state-issue

Logs

System Info

svelte: ^5.0.0 => 5.19.6

Severity

annoyance

[paoloricciuti]

It's because if you don't use $state you are in legacy mode where a normal object works. By spreading inside item.svelte.ts you are returning the object value rather than a reference to the signal.