-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
For some reasons, latest release are breaking my app #1777
Comments
You don't need to @ me, I see all messages (here and on Discord) 😀 Sounds like a regular old-fashioned bug. Can you show us a repro? |
Actually, it's strange, but I can't reproduce it in REPL using clean use case. I just know that if I update a version of Svelte, my app is breaking. (( So, seems something works differently than in the previous version. I'll try to reproduce it somehow but can't show exact code because it's commercial. I just thought you've some ideas about it. Maybe it's on the surface.
Deal )) |
I have problems with the new version too but in a different case. |
I'm also having a bunch of errors with 2.4.0. It seems like it has something to do with conditionals wrapped around loops. Some errors that I see are:
I'm not able to reproduce on the REPL though. I've had a few issues with reproducing deep use cases. I wonder if there's a way of tracking the different compilation scenarios. |
Does the behaviour differ between |
I'm still seeing these errors after 2.4.1. It's with both There was an Does the repl support the Store? |
This looks like it was reported in #1780 |
Is this issue still live, or was it the same as #1780? Does 2.14.2 fix things? |
Seems, it works on the latest release. |
@Rich-Harris
I don't understand why, but after update Svelte to the latest release, my app stops switching pages via <svelte:component />. Seems, it just adds the next page to the bottom, but the previous page does not unmount from the DOM.
If I downgrade to the previous version everything is ok.
Any ideas?
The text was updated successfully, but these errors were encountered: