Uncomfortable Svelte 5 DX using Inertia v2 + Svelte

[kresnasatya]

@inertiajs/svelte Version

2.1.2

Backend stack (optional)

No response

Describe the problem

When I'm using the Svelte 5 syntax in Inertia v2, I get uncomfortable DX like this: $page.blablabla and $form.blablabla. This is different when compare it with Inertia v2 (Vue/ReactJS). The reason is in Inertia v2, the Svelte 4 also supported. I'm not sure how many (literally) large scaled project using Inertia v2 with Svelte 4 syntax but with Svelte 5 it much more simpler thanks to the Svelte's runes. E.g. If we re-write the implemetation of usePage, useForm using global state runes, the DX will be improved. So, I just call like this: page.blablabla and form.blablabla.

If we want to keep support for Svelte 4, then we must split the packages: The packages/svelte4 for Svelte 4 and the packages/svelte for Svelte 5. So, we can re-write components, utilities in the package with new Svelte 5 syntax without disturb the Svelte 4 itself.

Steps to reproduce

Nothing.

[peaklabs-dev]

This would be a great improvement.

[pedroborges]

When Svelte 5 was released in October last year, Inertia v2 was still in development, so it was important for us to support both Svelte 4 and 5. I agree the DX can be improved by replacing stores with runes. I’ll take this back to the team and discuss the best path to make that happen.

[kresnasatya]

Also, besides that, we can use the new syntax of Svelte 5 like @render, @snippet to replace the <slot> tag.

[brodienguyen]

I did create a draft PR to give it a bit momentum, definitely need help from the core team as well as other Svelte developer help to make that dream come true soon.

• WIP - Add Svelte 5 adapter #2586