What a best alternative for FlowRouter now after lost arunoda and kadira?

[iamrommel]

Yet another abandonware. What if MDG takes over this project, there is no in-core/base package about routing for Meteor though.

[funkyeah]

Then do something about it.

That was kind of my point with my earlier comment

How should we as a community address the FlowRouter situation?
Is it important enough to attract some maintainers?
If so how do we as a community look for maintainers and make it easier and more palatable to volunteer in such a way?

@arunoda Do you think the these packages have a future or should the community move on?
Should the community fork or try to takeover the existing repo?
If the former, should we keep the same name or change it?
If the latter, what restrictions do you have on handing over the keys?

I’m not a very good developer but I try to contribute by digging as deep into issues as I can: https://github.com/kadirahq/flow-router/issues/551

I’d be more than happy to contribute $$ to a fund to keep flow-router alive, or bug bounties on issues relevant to me and others.

[vikr00001]

The days of MDG working on anything non-Apollo related are (almost?) over.

I don’t know why people keep saying that. MDG has a huge investment in Galaxy. Galaxy is a PAAS for deploying Meteor apps only. Under these circumstances it appears to me that there is no way MDG is going to abandon Meteor.

Apollo is the #1 thing Meteor needs right now because it brings access to mySQL, Postgres and other databases. It makes total sense for MDG to focus the majority of its development efforts on Apollo at this time. That doesn’t equal abandoning Meteor. It equals working hard on Meteor.

I look forward to reading other opinions on this important topic.

[ghabin]

Thanks for making things clear

If I had to do it all again, sure I wouldn’t use Flow Router or Iron Router or Blaze, but I made those decisions a couple years ago.

what your advice now . what alternative should I use ?

[maxhodges]

@ghabin

what your advice now . what alternative should I use ?

Clearly, FlowRouter for Meteor/Blaze and React-Router for Meteor/React. We prefer Meteor/React.

[maxhodges]

@cyclops

We want to make sure that we use maintained library and stack because we have a small start-up team with basic level and many times when we faced a bug on a library we only can wait until other guys fixed it and when we choose unmaintained library it’s increase my project risks.

Meteor 2017 Roadmap: Sourcemaps please

Almost every single breaking change since Meteor 1.0 is a bug (except some issues with build plugins). The best thing you can do to ensure this keeps working is stay up to date with the newest versions, and test out the beta releases and file bugs when things stop working for you. What format could this commitment be in? What’s the definition of “compatible”?

[ghabin]

Thanks alot
ok ,I will start in the Meteor/React direction
Regards

[cyclops]

@maxhodges we don’t talk here just about Meteor core. We are talking about packages dependencies like Flow-Router.
I saw that Vue.js also very attractive. I think Vue.js and Vue-Router or React and React-Router is the future of this part and best alternative to Flow-Router because it has bigger community and more maintainer for example if we compare Flow-Router VS React-Router it’s a general results:

Github Stars: FlowRouter = 1019 < React-Router = 17956
Github Forks: FlowRouter = 129 < React-Router = 4222
Github Contributors: FlowRouter = 38 < React-Router = 344
Github Last Commit: FlowRouter = 8 months ago < React-Router = 8 days ago

So I think based on this thread until now react-router and vue-router are wins and both Blaze related router (IronRouter and FlowRouter) are loser.

[maxhodges]

OK to be honest I have no experience with Vue. But it sounds pretty good. So I guess the best recommendation is:

• FlowRouter for Blaze
• Vue Router 2 for Vue
• ReactRouter for React

I think the anxiety about FlowRouter is unfounded. People can build with it. It works and will continue to work, and if for some reason it stops working, it’ll get fixed. But it seem others want some kind of FlowRouter support SLA That’s possible too if people are willing to fund it.

[theara]

I found [FlowRouter Extra](https://github.com/VeliovGroup/flow-router).

[NotaSRSbiz]

Does anyone have any router suggestions for a mobile only map app using ionic & leaflet?

[satya]

https://github.com/VeliovGroup/flow-router

Great find. I use Veliov Meteor Mailer and I’ve contributed to it (awesome package btw). I find their devs replying very fast and to be very helpful. Last commit to Flow Router Extra was 10 hours ago, so that looks very good.

[gdc3]

We started off with Iron Router, but ran into counter-intuitive weirdness and so dropped it. We looked at the then-nascent Flow Router, but found its API a little clunky and Arunoda’s comments about future direction at odds with our goals.

Given a bias for Express’ elegance and a belief that, yes, a router should only route — we baked PageJS into a package (along with Express for a server-side REST API). We’ve tweaked PageJS to make it more Express-like, particularly with regard to error-handling, and I expect we’ll further that over time.

Thus, I’d recommend PageJS as an easily digested library that gets you vanilla routing client-side. I’m happy to post our router package if someone’s interested in using it.

[dr.dimitru]

I’ve seen flow-router-extra is already mentioned here.
Thanks for everyone who already using it.

And everyone who is looking for up to date FlowRouter is welcome to try flow-router-extra. We keep all dependencies up to date, test it with every Meteor release, and publish updates when necessary.

Although it’s a fork of original FR, it’s extended with:

• Latest features - ES6 Import support, latest qs and page NPM dependencies
• Missed hooks - waitOn, data, onNoData and whileWaiting
• Ability to preload Images, Fonts and other resources
• No need to use BlazeLayout, efficient render with support of yield, layouts and with respect to requestAnimationFrame is build-in

Thanks to @theara for pointing me to this thread

[cyclops]

And everyone who is looking for up to date FlowRouter is welcome to try flow-router-extra. We keep all dependencies up to date, test it with every Meteor release, and publish updates when necessary.

It sounds good.
@dr.dimitru Thanks for join us in this thread with your awesome Flow-Router fork

[ramijarrar]

Have you considered reaching out to @arunoda for maintenance rights in the original repo? This would avoid much of the mess associated with a transition like this (i.e migrating issues, broken links, promoting new namespace, etc.)

[dr.dimitru]

@ramijarrar I don’t think @arunoda seeking for merge. As he is not share my vision on some features - see this Twitter post

Anyways, @arunoda - if I’m wrong, I’m ready to merge and put my hands on original FR as maintainer

[aido179]

Dimitriy, how do you address Arunoda’s points about waitOn essentially turning FR into IR?

[sashko]

I personally think waitOn was one of the most confusing (and UX harming) parts of IR, so putting it back is kind of going back on one of the main reasons to use FR. I think FR got one huge thing right: The router should act as just another source of data, rather than doing things like data loading etc.

[dr.dimitru]

imho, do not use it if you don’t need it.
Or it’s uncomfortable to know want such functionality is implemented?