Confusing output by `$inspect.trace`

[mtsgrd]

Describe the bug

I am trying to debug an $effect block using $inspect.trace, but the output gives me a no context for the various $derived and $state nodes in the tree.

I see in a simple playground example that it typically prints the value of the dependent variable inline. Is there an easy to understand reason why I am not seeing the same locally?

Playground example: https://svelte.dev/playground/16348415b1a44cb1b2390885c204f677?version=5.30.2

Reproduction

I can't repro using the playground, but I am using the same version as the playground: 5.30.2

Logs

System Info

System:
    OS: macOS 14.1.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 3.21 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.16.0 - ~/.nvm/versions/node/v20.16.0/bin/node
    npm: 10.8.1 - ~/.nvm/versions/node/v20.16.0/bin/npm
    pnpm: 9.9.0 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 136.0.7103.114
    Safari: 17.1.2

Severity

annoyance

[paoloricciuti]

In the CreatedAtError you should see the stacktrace that lead you back to the place where the derived/state was declared