Conduitry
Conduitry
I don't know what the `false as true` is supposed to do, but it does seem weird that the `as true` affects the scoping. To me, the issue is that...
I'd still like to argue for providing a way to run only this migration (and other future migrations we write that are for upgrading Svelte 4 code to non-runes Svelte...
`const selectedEmails = $selectedEmailsStore && selectedEmailsStore.getSelectedEmails();` in Svelte 4 isn't reactive, and so the migrated runes code is also not reactive. Something like `$: selectedEmails = $selectedEmailsStore && selectedEmailsStore.getSelectedEmails();` _is_...
Manually suppressing the warning like that if you know what you're doing might be the best option here. Having a special case for promises in the runtime feels dangerous -...
Closing this in favor of #15200.
This is what https://svelte-5-preview.vercel.app/docs/runes#$state-snapshot is for. I don't know whether it makes sense to patch `structuredClone` in dev to print a warning about this. There's going to be a never-ending...
I think you should be able to create a `.svelte.js` exporting a function that uses `$state.snapshot()` and then import and call that function from elsewhere in regular `.js` files.
This appears to be fixed in the new site.
The `[class]` selector doesn't match the `class:` directive, either. These both feel like real edge cases to me, though.
It is by design that the client-side not know about all of the server routes, because that's additional data to send to the client which it (generally) doesn't need in...