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
Svelte 5: Mutating property of passed in object locks up browser #11507
Comments
I've ran into this as well
|
It would be good to get a REPL of this if possible. |
Here's a live version: https://stackblitz.com/edit/sveltejs-kit-template-default-bhlpxc |
Can you make a REPL please? |
Sorry, I don't know how to reproduce it in a REPL |
The StackBlitz project also does not seem to reproduce the problem? |
You probably need a lot of items to make it obvious, |
You are right, since there are no interactive elements, it is just not directly apparent that anything broke. Wonder why that does not happen in the REPL, though... |
Dunno, I tried lots of different combinations and was never able to get it to trigger the same behavior. |
I am experiencing similar issue, however, in my case:
I'll try to isolate and extract a simple reproducer |
@singlyfy Are you mixing Svelte 4 and Svelte 5 components? It could be that the |
@trueadm : project itself is a mix of v4 and v5, specific component is converted to v5. I'll try to run it in a clean v5 project to see if that makes any difference. |
Describe the bug
Running in Svelte 4 / non-runes mode.
Sorting a child array on an object property passed in triggers reactivity as though the passed in property changed (it's not using bind) resulting in the browser locking up.
Seems to happen if data comes from a SK
load
fn, and is then passed from the page to a component that changes it (without using bind)Pausing the code sometimes breaks at the error shown below.
Reproduction
+page.js
+page.svelte
Component.svelte
Logs
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: