-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
5.19.1 breaks untrack #15077
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
Comments
Hunch: it's this: #15065 |
Confirmed locally, reverting #15065 does indeed remove the error. |
I'm looking into it. |
Has it been released? I'm also noticing errors and rolled our application back to
|
It has just now |
Tried updating to 5.19.2 and reactivity seems to be broken somewhere around the REPL I've posted here. Will try to come up with modification to show reproduce tomorrow. |
Interesting, I look forward to seeing what it is, maybe we missed something else. |
I still get those errors, even though If I remove all usages of untrack in the whole code base. Any idea what it could be or how to narrow it down? // edit: Ok, it comes from $state management or sth like this. Maybe related to bits-ui |
Describe the bug
Our app becomes broken after update to 5.19.1 perhaps due to #15065
Reproduction
UPDATE: REPL
Works fine for me if I switch to 5.19.0
Logs
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: