No arguments here bro, when I started with Meteor, I skipped IronRouter just because of that, didn’t even bother looking at the docs. I used FlowRouter right away, even though I had a hard time starting with it for a while (I really need to brush up my skills lol).
But like I said, I needed Client and Server side routes, and when I looked for other ways to whip up server routes, it got me to many places, which gave me headaches.
That’s when I considered looking at Iron Router, I thought to myself, “hey Iron Router says its both Client and Server routes, maybe I should take a look, and having one library to handle both routes might be a good idea”. When I saw the docs, it actually impressed me because I find it not only concise and somewhat complete, but also it’s beautiful enough not to be an eye sore. It’s organized as well.
Then I found out people are actually using it until now for large apps with relatively high demand that has business around it (@vlasky to name one). That’s what convinced me to use it because, if ever a problem pops up with Iron Router, I know people will jump in and fix it (hopefully I can help too).
And the fact that nothing major broke it yet, for me, is a major feat.
For the jquery issue, you can look here.
I’m using it with the latest jquery from npm, no issues yet.
Even Meteor is using the latest jquery now.
- Open
.meteor/packages - add “@3.0.0!” to jquery, without the quoutes (jquery@3.0.0!)
- Install Iron Router as usual (
meteor add iron:router)
This will tell meteor to skip the packaged jquery and use the one from npm, and tell other meteor packages to ignore their version specific jquery dependency (which is usually version 1.x.x).