Svelte 5 $state() not properly logging values when using @235 but works in @220

[itsmikesharescode]

Describe the bug

I was using the latest version 5.0.0-next.235 but find out this weird $state behavior when logging in the browser.

Not working version 235

Working version 220

Reproduction

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA31R0WrDMAz8FSEGaSE072kSGP2EPdZ9cBM1MXVlL1a6lpB_H25SKGPb25046U7SiCdjKWC-H5H1hTDHd-8xRbn7SMKVrBCmGNzQ17FShLo3XsBqbkuFEhRWipVYEtAcvqjfORZtmHoo4S2IFlqNUaEkOuSQJOlMPwcKYhyHHPZzRcn4BErEiH2Vv7bksD88q9MMHnxabxVHUDsOAp3mxtLHcLwYgRJWaygrWCyiwlnaWNeufgTfxKApJNKZAL43LIZbkI7gqu1AycPk_xHPbnby94Rpq7jI5oPGI3LhqyWs5jsI3SJooO6oPsPiBta1ReZnvWE_CMRnxV_QTRTC0XCTP2zK8bfFJsgqxcVxEHEMjmtr6nM5vt5qWmIU2ayqFGOKF9eYk6EGc-kHmg7TN-e8ZXU-AgAA

N/A

Logs

No response

System Info

System:
    OS: Linux 6.8 Linux Mint 22 (Wilma)
    CPU: (8) x64 Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz
    Memory: 6.12 GB / 11.55 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 20.13.1 - /usr/local/lib/nodejs/bin/node
    npm: 10.8.0 - /usr/local/lib/nodejs/bin/npm
    pnpm: 9.1.0 - /usr/local/lib/nodejs/bin/pnpm
    bun: 1.1.25 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 127.1.68.134

Severity

blocking an upgrade

[brunnerh]

Please do not screenshot code or output.
It cannot be copied easily (and is inaccessible).

Also, a proper description of what is expected and what actually happens would be helpful. It is hard to decipher what exactly is going on there.

[dummdidumm]

Is this about the apparent inconsistency between what you see when inspecting the whole $state object, clicking on the Target property of the Proxy and then seing that the string is empty but you expect BUG test! to be present in there?

[itsmikesharescode]

Is this about the apparent inconsistency between what you see when inspecting the whole $state object, clicking on the Target property of the Proxy and then seing that the string is empty but you expect BUG test! to be present in there?

yes sir is this normal?

[itsmikesharescode]

Please do not screenshot code or output. It cannot be copied easily (and is inaccessible).

Also, a proper description of what is expected and what actually happens would be helpful. It is hard to decipher what exactly is going on there.

sorry i tried my best still beginner in web dev

[brunnerh]

Looks like the proxy no longer modifies the original object (demo).
The property values are stored in a separate Map.

(I would recommend to use $inspect for observing state, or use $state.snapshot to get a realized copy of the current state.)

[itsmikesharescode]

Looks like the proxy no longer modifies the original object (demo). The property values are stored in a separate Map.

(I would recommend to use $inspect for observing state, or use $state.snapshot to get a realized copy of the current state.)

Copy sir, thank you for this.

[Rich-Harris]

Closing as this is working as intended. It's very unfortunate that browsers print the target object rather than what the proxy itself reports as being its contents, but that's life on the cutting edge for you (other frameworks have the same issue, it's not just us).