Don't use global router instance for SSR

[fabien]

Hi @lyohaplotinka,

As a follow-up, I was able to get SSR running eventually - the component module signatures for SSR are different, and I was expecting a specific kind in order to hook everything up.

However, I started to notice an unexpected side-effect of global.$$$easyrouteRouter being a router instance.

Since I had implemented some of my own beforeLeave hooks (as shown in the Sandbox.io demo I sent you by email), I saw how SSR requests were suddenly 'stateful': beforeLeave was triggered with the last visited url, even though the server should not actually be aware of this (as it could have been any request, not just mine).

In cases like this, it's always better to opt for a 'shared-none' approach, and solely operate within the boundary of a single request. As such, one should create a new router for every request - perhaps some optimizations can be made within easyroute-core which only recreates the 'history' for SSR (or better yet: doesn't keep anything stateful around).

Please have a look at the code. My solution piggy-backs on the current global.$$$easyrouteRouter but only to get the factory function that creates the router on each request. I'm sure there are better ways, but it's only to give you a general idea.