Support for serverside environments

[ItsRealmy]

Not sure if this is the best place to make a feature request, but here goes:

I love the simplicity of this package, this is exactly how routing should be. However, due to the use of the document variable somewhere in the code, I'm not able to render any component with this router on the server (using Component.render()).

Could there be a way to pass a url prop to the router in order to make it work on the server, similarly to how svelte-routing does it?

[ayndqy]

Hi @ItsRealmy,

Unfortunately, the current architecture of the library makes it impossible to pass a url prop to the Route component.

However, I am currently working on the version 3 of the library where the behavior you described will be implemented using the source prop:

<!-- Root route -->
<!-- `source` is any string value that the route tree will rely on to render routes,
     in this case it's a reactive store which contains a path extracted from url -->
<Route source={$path}>
  ...
</Route>

This solution is designed to support different types of routing (hash, in-memory), but it can also be useful for server-side routing, as in the case you describe.

I have no experience with server-side routing, so any ideas on how to implement it would be appreciated.