An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.3.0
Type	devDependency

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

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/blinkmobile/blinkmrc.js/builds/238815268?utm_source=github_status&utm_medium=notification) - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/blinkmobile/blinkmrc-js/build/1.0.68)

Commits

The new version differs by 10 commits.

44ca158 update utils changelog
a3728d7 bump eslint-module-utils to v2.1.0
3e29169 bump v2.4.0
ea9c92c Merge pull request #737 from kevin940726/master
8f9b403 fix typos, enforce type of array of strings in allow option
95315e0 update CHANGELOG.md
28e1623 eslint-module-utils: filePath in parserOptions (#840)
2f690b4 update CI to build on Node 6+7 (#846)
7d41745 write doc, add two more tests
dedfb11 add allow glob for rule no-unassigned-import, fix #671

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

oneblink / blinkmrc.js

An in-range update of eslint-plugin-import is breaking the build 🚨 #19

Version 2.4.0 of eslint-plugin-import just got published.