-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client errors aren't that helpful in the docs #14752
Comments
I'm having an hard time finding what could be it's cause too. |
Can you post the code @Aryxst? @Rich-Harris asked for real life examples to give a better explanation in the docs |
I'm getting this error on a local unpublished repo. I will create a repo/repl and share it in a couple hours |
https://github.com/Aryxst/chimera/blob/master/src/routes/settings/sources.svelte Edit: It's weird because I get the error after like the fifth time the state |
I've managed to trigger this error again, and it's really difficult to trace what derived/template expression causes this error to occur. If the error logging from Svelte could show the derived/template expression that ran when this was triggered would drastically help me in debugging @Rich-Harris |
I've managed to trigger the
Svelte error: state_unsafe_mutation
error a couple of times while migrating my app from Svelte 4 to 5. When it happens i am a little confused as to why, and when i click on the link to the client errors in the docs i get no further explanation on common use cases, how it can happen and what to do to solve it: https://svelte.dev/docs/svelte/runtime-errors#Client-errorsIt would be awesome if the docs had deeper explanations on these errors, so that i could use it as a resource for fixing the bugs that occur. I would imagine that people who google these errors would be pleasantly surprised to find an explanation and solution to these errors in the docs.
The text was updated successfully, but these errors were encountered: