SSR: Make the Route component register during initialization

[webJose]

It occurs to me that the code that registers the route in the router could run, with initial parameter values, during the initialization of the Router component. This will enable SSR of all matching routes.

As it currently is, this only happens during an effect, and effects don't run on the server. There are no errors, but no content renders either.

This, however, doesn't affect @svelte-router/kit, as hash fragments never reach the server, and @svelte-router/kit can only do hash routing (single or multi).

This would be for custom SSR frameworks/scenarios that use path routing.

I'm setting the priority to Low for now. Interested people: Upvote to change to a higher priority.

[webJose]

In the potential v2.0 architecture, Route components could be made to SSR appropriately for more than just the initial value of the path and and properties. Since they would own the code to match routes, its matching reactive value can be a derived value that lives within the component, making the current effect approach unnecessary for content-displaying purposes, making the component SSR-compliant.

Sounds promising.