The short answer is to combine it with Template.dynamic. The longer answer is coming soon in the form of a new package 
2 Likes
If you’re using React already I would recommend just switching to React Router, even if it’s not quite as user-friendly as FlowRouter.
3 Likes
If you have the time to explain this more, please do.
There’s not much to explain. You just have to bite the bullet and migrate to React Router. The reason I say it’s not as user friendly is that whereas FlowRouter usually has an easy enough API to do various things, React Router is very “React-y” and requires using things like higher-order components which are not very intuitive when you’re just getting started. But at least you know that you’re doing things the “correct” way for the React ecosystem.
1 Like
Looks like the Kadira team went off to do Storybook and are completely ignoring all messages about their previous work. That is really sad, since they were such an important part of the community here. Now we can’t even get a single message out of him.
2 Likes
Sad indeed. Now if you’d like to contribute to FineRouter (aka FlowRouter), please PM me on here or github and I’ll give you a contributor role or just submit a PR and if it makes sense I’ll pull.
That’s the price of free open source software.
4 Likes
Im afraid for the whole mantra project, having a big app depending on it.
mantra has luckily not much code itself. It’s basicly just some wireing.
I hope mantra get’s some more momentum from the comunity. I currently use it a lot and thing this is really a good approach.
But I also hope that @arunoda and co. start looking for contributors for their repositories. I understand that they currently want to focus on storybook, but they should at least open their repositories to the community, if they do not want to maintain them.
1 Like
I’m all for Iron-Router that is what I use. But it seems that the major part of the community is moving over to Flow Router which is also been recommended by a number of people. As a package owner I think it’s correct to support both.
+1 for removing iron:router dependency and make it easier to use houston together with flow-router.
Hi guys,
has the community already decided which package to use for FlowRouter’s future? We should ALL use THE SAME ONE instead of creating our own folks with little fixes here and there (p.e. see Spacejam phantomjs no route for the path /local flowrouter).
@sashko: How about putting a recommandation for FineRouter (or another package that you recon) in meteor guide, so that the existing energy gets bundled?
The FlowRouter is in the Guide and since it is a project of Kadira it might be logical for MDG to maintain it, following the news of them buying out Kadira.
1 Like
We’re not going to become the primary maintainers of flow router, but I’d be happy to replace the link in the Meteor Guide to point to a different package - is there one that a lot of people are using as a replacement?
I’ve been using FineRouter - FlowRouter fork - for a while now. Maybe we can use it as a replacement if @aadams continue to maintain it?
1 Like
Flow Router is fine in my experience. Does basic routing and that’s all I want from it. React Router is also an obviously great alternative.
Not sure why everyone is freaking out for no reason.
4 Likes
https://github.com/VeliovGroup/flow-router Seems to be a much more actively maintained and feature-rich version. VeliovGroup also maintains several other very useful Meteor packages and @dr.dimitru is really quick and responsive. You could consider their fork too 
3 Likes
I think a good first step would be to ask the community if someone(s) would like to take over maintenance of FlowRouter. It’s still very fit for purpose and IMHO the best outcome would be for it to continue being supported by the community