Svelte 5.1.5 breaking vaul-svelte animation

[WarningImHack3r]

Describe the bug

Svelte 5.1.5 breaks the opening animation for vaul-svelte, when 5.0.0-5.1.4 is fine.

I don't know if the issue comes from Svelte or Vaul though. References huntabyte/vaul-svelte#52 (comment).

Reproduction

README demo in 5.1.4:
https://svelte.dev/playground/hello-world?version=5.1.4#H4sIAAAAAAAACm3OQYvCMBAF4L8S5rRCNfcaCuIevLks3jZ7iHaUQJqEyVhXSv-7dNOqiNeP995MB940CCVs0LkgLoFcLT6wtoz1DAo4WocJyp8O-BqH3ABQTK1VjIvUouPB9ibhOz8Ez-g5QQkqHchGrrTXbJsYiEUnPslckEQvjhQaoaE1ZzfPbQ1L7ZV8tLzK6cV3CHlmgh3Z0wmp2kb0Sr7gc_ArEBv3Tw9c5x9H1axiNZKSccrKt-FpYtsiOXMVMl-Tr-fuMr4OBTD-MZRMZ-x_-xusRn_tiwEAAA==

README demo in later versions (latest here):
https://svelte.dev/playground/hello-world#H4sIAAAAAAAACm3OQYvCMBAF4L8S5rRCNfcaCuIevLks3jZ7iHaUQJqEyVhXSv-7dNOqiNeP995MB940CCVs0LkgLoFcLT6wtoz1DAo4WocJyp8O-BqH3ABQTK1VjIvUouPB9ibhOz8Ez-g5QQkqHchGrrTXbJsYiEUnPslckEQvjhQaoaE1ZzfPbQ1L7ZV8tLzK6cV3CHlmgh3Z0wmp2kb0Sr7gc_ArEBv3Tw9c5x9H1axiNZKSccrKt-FpYtsiOXMVMl-Tr-fuMr4OBTD-MZRMZ-x_-xusRn_tiwEAAA==

Logs

System Info

vaul-svelte latest version

Severity

annoyance

[trueadm]

This is the release for 5.1.5: https://github.com/sveltejs/svelte/releases/tag/svelte%405.1.5. I can't see anything relating to transitions in it unless it's the effect ordering change from #14038, but that's a fix and how it should have always been.

I'm not sure if this is a bug in vaul-svelte.

[WarningImHack3r]

Yeah, checking the changelog was the first thing I did and I didn’t notice anything suspicious either…
But even as a Svelte user (vaul in that case) what could possibly have gone wrong with these changes to break anything in a lib?

Anyway, if you’re sure it’s not from your side then I guess it’s fine to close this issue, thanks for investigating!

[elliott-with-the-longest-name-on-github]

@huntabyte if you haven't seen this on your end yet

[aiyer07]

Facing the same issue @WarningImHack3r did you find anything other than downgrading svelte?

[WarningImHack3r]

No, I didn't

The only place I was using it in is no longer an active project, so I'm not particularly impacted anymore
But the bug is still there, and it'd be good to get it fixed by whatever's causing it