Open sparecycles opened 2 weeks ago
I think we should preserve the Svelte 4 behavior in legacy mode but introduce the more strict behavior in runes mode (so that we can eventually remove the logic of reordering them)
Svelte4 had too much magic. 😁
There's a third option which is requiring an additional flag for this logic (if it's primarily an issue for library-generated code, since client code can always reorder easily):
Pro
Con
Describe the bug
Filed an issue in melt-ui, https://github.com/melt-ui/preprocessor/issues/57 Cross-posting for visibility in case this actually is a larger issue in svelte's code gen emit ordering.
Reproduction
Starting with melt-ui's basic stackblitz setup:
See
{@const itemId = id}
usage in here: https://stackblitz.com/edit/github-suxd85?file=src%2Flib%2Fcomponents%2FAccordion.svelteIn case the stackblitz repo is broken, run
and change
Logs
Severity
annoyance