SSR error: Component.render(...) is no longer valid in Svelte 5

[harryqt]

Version:

• @inertiajs/svelte version: 1.0.14

Starting SSR server on port 13714...
Inertia SSR server started.
1132 |   $$payload.out += `${anchor}</div>`;
1133 |   bind_props($$props, { id, initialPage });
1134 |   pop();
1135 | }
1136 | SSR.render = function() {
1137 |   throw new Error("Component.render(...) is no longer valid in Svelte 5. See https://svelte-5-preview.vercel.app/docs/breaking-changes#components-are-no-longer-classes for more information");
               ^
error: Component.render(...) is no longer valid in Svelte 5. See https://svelte-5-preview.vercel.app/docs/breaking-changes#components-are-no-longer-classes for more information
      at /Users/harry/Projects/laravel-test/bootstrap/ssr/ssr.js:1137:9
      at /Users/harry/Projects/laravel-test/bootstrap/ssr/ssr.js:1175:35

[punyflash]

This is a huge breaking change since Svelte moving to functional components and will require rework for how the app is created. Right now, the server component is hard-coded in the adapter. Ideally, SSR app should be created from setup function exposed to devs in a same way as client rendered to avoid issues like this. I plan to implement it in my adapter soon, but it will require some undocumented steps from developers to configure it properly. As I'm not a fan of rewriting docs just for my adapter, in case there is no decision from inertia team since initial release of Svelte 5, I'll write docs as well.

[punyflash]

I was able to implement Svelte 5 SSR support - use @westacks/inertia-svelte@next version of the package. To setup SSR follow the guide here: https://github.com/westacks/inertia-svelte/tree/2.x

[harryqt]

Thank you so much for the hard work. I've tested it and it worked perfectly. 🎉

[buhrmi]

Nice, I like this more than my implementation. A PR when Svelte 5 is released would be cool