Updated the code style (and dependencies) for the full scaffold to match (as best as seems reasonable) the Meteor guide.
There is some discrepancy with the recommended eslint configuration. For example there are a number of rules that make sense within the context of a Meteor project, which is exactly why these have been added in the todos example. So to address that I've added a few
In some cases like this it is pretty much standard practise (in Meteor) to not bother with naming function expressions (
Perhaps a solution is that it can be handled by the eslint meteor plugin, though I'm not totally sure how that might work since it's designed to work independently to the airbnb rules. @dferber90 any thoughts? :)
So in the meantime until there's a solution like above should we remove the
abernix left a comment
Overall some great changes here!
As to the ESlint stuff, I'm really not up to date on the latest in