Update devDeps, fix lint error

[RyanZim]

@jprichardson Ever think of using @greenkeeperio-bot so I don't have to do this? I use it on all of my projects and really like it. Not only does it update dependencies outside your version range, it also checks to make sure none of your dependencies break semver.

My only gripe is the commit messages: chore(package): update eslint to version 3.8.0. I always use the squash-merge function so I can reword the commit message to Update eslint to version 3.8.0.

https://greenkeeper.io/

[jprichardson]

Thanks for this!

Ever think of using @greenkeeperio-bot so I don't have to do this?

I'm not a fan of it as I think that this promotes updating dependencies for the sake of updating dependencies as a good thing. This is not to say that I couldn't warm up to it, but I'm not ready for it yet.

[RyanZim]

I think that this promotes updating dependencies for the sake of updating dependencies as a good thing

Not sure what you mean by that, it only updates your deps when the latest version is not covered by your current version range. Mind elaborating?

[jprichardson]

Not sure what you mean by that, it only updates your deps when the latest version is not covered by your current version range. Mind elaborating?

Sure. There's a unforeseen cost when updating dependencies. You rarely don't know what it is up front. Greenkeeper and the like promote that to have stable and usable software, you must update your dependencies. Software developers feel good about this - one more thing to check off the list. I'm saying that these services don't show the unforeseen cost. I believe it's the developer duty and responsibility to be judicious about updating and the need to update.

Please feel free to ask more questions about this if you have them.