adiGuba
adiGuba
On large applications, a migration can be long and complex, and an automatic migration may not be sufficient/complete. I think it is important to have a way to migrate components...
I just added an alternative syntax using a module-const field : ```svelte const svelte4_compatibility = { slots: { header: true, footer: true }, events: { click: true, custom: true }...
The result of the migration has some limits : * Some thing are not migrated, like **createEventDispatcher()** that still use old-events style via the `on:event` directive. * Event bubbling `on:event`...
I understand that the migration script has imperfections (and that normal). And I'm not necessarily talking about that. Currenly, it's easy to replace a slot with a snippet, or an...
Just in case, I make an alternative solution using a Vite plugin : https://github.com/adiguba/svelte4-bc Should I close this issue ?
Hello, It seems that the problem come from these lines : https://github.com/sveltejs/svelte/blob/c73c683ecdb96ce27c31a7272287d30bfb41c861/packages/svelte/src/internal/client/dom/elements/transitions.js#L345-L351 => The dummy animation with a delay of 0 instantly gets the 'finished' status. But for some reason...
Another solution could be to use a small but non-zeo delay, like `out:fade={{delay:0.00001}}` https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACo1SwU7kMAz9FSuLxIzE0uHabbtC4hO40T10EneISOOQuKBR1H_HCaNdbmzVqnb8nv1sJ6vZOkyqfcrKTwuqVt2HoG4Un0Nx0hs6RvETrVGXky7paAMPox_ZLoEiQ4Z5MggbzJEWuP7kNBwnnyxb8tcFWz6HDBTQQw9XiSfG3Ty5hPtfEpTwlfUpoOZdwexH3zX_avn8w86VvBVoZ-wbJD477Ed1nPTLKdLqzU9NjmILEc2owPq2CqOVq9HnbNBN5_Zwe5DnbttqF5ItDPxsE8jLdDo5nI4OQZNn9Nw1ocK6RmqKlRs7Fw2-O67M5IG8dla_9Hm374d86Y_jipK_eF3zCRy-odRZCEc7SvgtqUh6t97Q-21CfrQLSpu7v6GRv2YtJ9sNHPb_yyryL6Q7IYmq11Vqu_NlQF_lheGhLOOZVmfgiC3Uhn7DqMpf9tCKWZuSpWxlnHKfFjJ2tmhUWyf1Z_sAnYKTTYoCAAA=
Oh it's work on Firefox but not Chrome. The latter seems to need a delay of 0.001 instead of 0.00001...
Hello, > Btw, since #12507 ([email protected]) snippets aren't signed anymore and you can try to pass any function as a snippet (though you still can get a typing error in...
Why not use **createRawSnippet()** ? ```js const children = createRawSnippet(() => { return { render: () => "Hello World" }; }); ```