Nested Routers

[posva]

What problem does this feature solve?

Allow using nested memory routers to handle independent views. e.g. the messages on Twitter, or a chat.

A custom History implementation could even save the current page in local storage and restore it when reopening the app.

What does the proposed API look like?

provideRouter(createRouter(...))
// or
createNestedRouter(baseRouterOptions)

• Could warn if history is based on HTML5
• No initial navigation
• Should provide these
• Could appear in devtools
• Could automatically unregister the history listener on unmounted
• Should not change global configs
• Should still be able to access the global router

[posva]

This would have to go through an RFC to better identify the different needs of creation/destruction of nested routers.

[Bertie2011]

The use case I have is having independent movable windows in an app with their own navigations. I also could imagine this being useful for plenty of gamified apps (e.g. a shop/menu sidebar that has multiple levels to it)

[brendomaciel]

It's a pretty nice feature. It would address this scenario I guess.

[kissu]

Could also be useful in the use case of some micro-frontends where there are a lot of moving parts and people want to have it fully dynamic. Having 2 nested routers doesn't work so well right now.

PS: the current state of this issue is the following:

• not enough interest
• too much work
• need a RFC still

Got this info from posva himself on the Discord server.