What are production quality router options for the mobx-state-tree-based web-apps?

[SergeyVolynkin]

Greetings,

I've searched over the internet and didn't get a good understanding / didn't find good suggestions on what routing library should be a good fit for the mobx-state-tree-based web-apps

Maybe someone from the MST community can share their production experience?

[SergeyVolynkin]

My thoughts that

1. kitze/mobx-router Is an interesting candidate
   • Cons:
     • there is lack of documentation on how to use kitze/mobx-router + mobx-state-tree together
2. react-router should be a robust solution that most of the FE devs know & used before
   • Cons:
     • As far as I'm concerned it's not easy (possible?) to separate data-fetching from component lifecycle methods (e.g. like kitze/mobx-router allows with beforeEnter: () => {…})

cc @mweststrate @kitze @ryanflorence would really appreciate your opinion if you have a few min.

[kitze]

@SergeyVolynkin check out rttr (not maintained btw)

[mweststrate]

See also https://nareshbhatia.github.io/mobx-state-router/ / https://github.com/miles-till/mobx-state-tree-router. No personal experience with any of them.

…

On Fri, May 21, 2021 at 11:49 AM Sergey Volynkin ***@***.***> wrote: My thoughts that 1. kitze/mobx-router <https://github.com/kitze/mobx-router> Is an interesting candidate - Cons: - there is a lack of documentation on how to use kitze/mobx-router <https://github.com/kitze/mobx-router> + mobx-state-tree <https://github.com/mobxjs/mobx-state-tree> together 2. react-router <https://github.com/ReactTraining/react-router> should be a robust solution that most of the FE devs know & used before - Cons: - As far as I'm concerned it's not easy (possible?) to separate data-fetching from component lifecycle methods (e.g. like kitze/mobx-router <https://github.com/kitze/mobx-router> allows with beforeEnter: () => {…}) cc @mweststrate <https://github.com/mweststrate> @kitze <https://github.com/kitze> @ryanflorence <https://github.com/ryanflorence> would really appreciate your opinion if you have a few min. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1721 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN4NBBUIKU6SD2UPSFKGSDTOY3B7ANCNFSM45I4G6AQ> .

[SergeyVolynkin]

Thanks, @mweststrate! I'll look into these

If it's okay to ask, what do you tend to use in your prod projects for routing? (together with mobx/mobx-state-tree)

[SergeyVolynkin]

@nareshbhatia if you have a few minutes, may I ask for your recommendations on the topic?

[nareshbhatia]

Hi @SergeyVolynkin, I am not experienced in mobx-state-tree, so don't know if mobx-state-router will work with it or not. All I can say is that the the router is well documented (see here). Please feel free to try it and let me know if it works.

P.S. Note that mobx-state-router version 6.0.0-beta.2 supports mobx-6

[SergeyVolynkin]

Ack, thank you @nareshbhatia

[EmilTholin]

Michel's blogpost How to decouple state and UI is still a favorite of mine all these years later. It outlines how to invert the concern you have with React Router with vanilla MobX, but it's straightforward to migrate the concepts to MST.

[paxarpp]

Hi, i used https://github.com/alisd23/mst-react-router