latest svelte@5 broke its tests

[yanick]

see #352

[yanick]

Reported to the mothership, in case it could help: sveltejs/svelte#11228

[mcous]

Weirdly enough, I cannot reproduce this failure locally on the same Svelte version

❯ npm why svelte
svelte@5.0.0-next.108 dev

I wonder if there's a race condition here? Maybe tick() isn't fully flushing updates, and that's what CI is hitting

[mcous]

More testing results:

• svelte@5 accessor tests pass with @sveltejs/vite-plugin-svelte@3.0.2
• svelte@5 accessor tests fail with @sveltejs/vite-plugin-svelte@3.1.0

Will add this to the thread over in svelte, too

[mcous]

Oh hm mothership issue has been closed with a fix that "preserves accessors with HMR." That's odd, because we have HMR disabled in our test suite. Will wait on the next.109 release though and see what happens

[mcous]

@yanick looks like this has, in fact, been fixed upstream. Your report did the trick. I can no longer repro locally nor in CI

[yanick]

W00t! That was easy. ^.^