Flow-Router-Extra vs React-Router

blaze
1

Hi,

Our Meteor application has mix of Blaze Templates & React components. Majority is Blaze templates but all new UI we are creating as React components. We are using iron-router until now but with Meteor 3.x we have decided to migrate iron-router code using a different router because iron-router code has Fibers which is no longer supported to latest nodejs. We are considering Flow-Router-Extra or React-Router. I want know if there are any recommendations on which one is good for our application and why? Also is there any official recommended routing package from Meteor?

2 Likes
2

Hey @mohan1304, if your project uses both Blaze Templates and React Components, I think the best option is to use Flow-Router-Extra.

@dr.dimitru recently shared a blog post about the latest Flow Router packages update: Meteor.js: FlowRouter packages update - DEV Community.

1 Like
3

Hi @fredmaiaarantes, Thanks for your response.

My concern is, this package is community supported and I’m not sure how long this will be actively maintained so little worried to use for production environment. Because if for some reason if the support for this package stops and if we face any issues then its going to be rework for us to go with different router. For example, our current code is using iron-router which will not work with latest nodejs because of Fibers dependency but its not maintained anymore so we have to change our current code which is a rework for us.

I still have below questions

  1. Is this package officially recommended from Meteor Team for routing? If so will there be long-term maintenance or support for future technology changes (like any nodejs deprecations, etc.)
  2. Do you have any plans to include Flow-Router-Extra package or build your own routing package as part of Meteor framework itself? This will help in avoiding above situation.
4

@mohan1304 answering your questions:

  1. It’s officially recommended and mentioned in the docs, guidelines, tutorials
  2. I’m planning to eventually decouple it from Meteor to NPM ecosystem. Where it will turn into twi packages BlazeRenderer as Atmosphere/Meteor package. And flow-router as NPM package. No timelines on this, just assuring you that this package has future
  3. Regarding its maintenance — I’m developing and maintaining these packages since 2015 and backed by veliovgroup company

P.S. Regularly supporting open sources package you rely on is a good way to ensure it will remain up-to-date and maintaned

2 Likes
5

I can really recommend flow-router. This is a great package.

2 Likes