eslint-config-mongodb-js@2.2.0 breaks build ⚠️

[greenkeeperio-bot]

Hello lovely humans,

eslint-config-mongodb-js just published its new version 2.2.0.

State	Failing tests ⚠️
Dependency	eslint-config-mongodb-js
New version	2.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build kept failing.

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

The new version differs by 19 commits .

• 6470d22 2.2.0
• 7bf3c86 disable rule: consistent-return (#39)
• e3afb09 2.1.1
• 50dc843 2.1.0
• 296d0b8 make eslint a real dependency / bump versions / rename deprecated rule (#38)
• c656302 2.0.1
• a148aa3 update react rules, rule definition changed. (#32)
• 3fa4ffb :fire: space-after-keywords
• a80dabe space-return-throw-case :arrow_right: keyword-spacing
• a6858ee no-empty-label :arrow_right: no-labels
• c88e937 chore(package): update eslint-plugin-react to version 5.2.2 (#21)
• 3f04d30 Merge pull request #18 from mongodb-js/greenkeeper-eslint-plugin-react-5.1.1
• 42cfcb6 chore(package): update eslint-plugin-react to version 5.1.1
• 3022e1a Merge pull request #14 from mongodb-js/greenkeeper-eslint-2.5.3
• 294822d chore(package): update eslint to version 2.5.3

There are 19 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}

---

This change is

[mention-bot]

@greenkeeperio-bot, thanks for your PR! By analyzing the annotation information on this pull request, we identified @imlucas, @rueckstiess and @kangas to be potential reviewers