Hey guys! I’m looking forward to use the newly released FlowRouter together with @splendido’s Useraccounts package and considering this little discussion, I wonder what are the ways to make it possible without using two routers in my app?
@joshowens
My biggest question is what happens if I install a package like useraccounts that has Iron Router in it?
Will we have to build new packages that use Flow Router instead of Iron Router, or can they live side-by-side?
I am also very interested in this and the response I seemed to get from @arunoda centered around having pacakges that don’t implement routes, but I think there is still a strong use case for building bits of functionality that have urls in them. A url is a basic building block of the web and it really makes me sad that we don’t have a core direction from MDG on this.
Iron-Router came to us at a time when Router just wasn’t cutting it. While I do think Iron-Router is cool, I do think it is very hard to reason about and understand when things are re-rendering and why they are re-rendering so much. I think Arunoda is really on to something interesting with FlowRouter and I want to see that work continue, but we have a large package ecosystem that has coalesced around Iron-Router.
My question is, how do we as a community thwart this type of ‘Router lock-in’ and give ourselves the freedom of choice while still being able to build routes into our packages
Just to let you guys know in case you missed it, there is a cool new package Router-Layer that could be useful in making Useraccounts more router-agnostic.