sveltejs / svelte · Issue No. 18468
With forking enabled a 'disabled' bits-ui tooltip will read a derived value that is no longer valid.
issue is not present without forking.
I initially found this error when using the forkPreloads option in sveltekit, when navigating away from a page with a disabled tool tip where the tooltip depends on a derived value the page would show an error boundary.
i was unable to replicate without bits-ui, but i am inclined to believe this is a svelte issues based on the error only appearing with forking enabled.
[!NOTE]
without the error boundary the error is still thrown and logged to the console, but the application continues to work. its possible this is actually just the boundary catching the error from a fork when it shouldn't but it seems odd the exception would be present at all.
https://svelte.dev/playground/5fbf63a8ae1c4fc98e24d28616491ee3?version=5.56.4
there is a disabled bits-ui tooltip with 2 buttons below.
button on the left will create a fork clearing the lines and allow you to commit.
upon commit the boundary will trigger and an error will appear in the console.
if you reset and click the button on the right the lines are cleared without a fork. no error present.
you can reset and try again.
{ message: "Line with id 2 not found" ,data: undefined }
TypeError
TypeError: Cannot read properties of null (reading 'error')
at invoke_error_boundary (playground:output:1350:41)
at handle_error (playground:output:1330:3)
at update_reaction (playground:output:5824:11)
at execute_derived (playground:output:2511:13)
at get (playground:output:6083:14)
at get disabled (playground:output:12168:29)
at getter (playground:output:8847:40)
at eval (playground:output:11964:28)
at get current (playground:output:9077:12)
at #register (playground:output:11622:40)
System:
OS: Linux 6.18 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900
Memory: 15.45 GB / 31.19 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.18.0 - /home/jayce/.nvm/versions/node/v20.18.0/bin/node
npm: 10.8.2 - /home/jayce/.nvm/versions/node/v20.18.0/bin/npm
pnpm: 10.18.0 - /home/jayce/.local/share/pnpm/pnpm
bun: 1.1.15 - /mnt/c/Users/jjones/AppData/Roaming/npm/bun
annoyance
Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.
The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.