Adding eslint generates multiple unmet peer dependencies

[MikeTheCanuck]

Installed eslint (with airbnb styles, react=true and JSON config file) in the eslint-enable branch.

Now when I fire the yarn command in this branch, it results in these warnings:

$ yarn
yarn install v1.3.2
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " > eslint-plugin-import@2.8.0" has unmet peer dependency "eslint@2.x - 4.x".
warning " > eslint-config-airbnb@16.1.0" has unmet peer dependency "eslint@^4.9.0".
warning "eslint-config-airbnb > eslint-config-airbnb-base@12.1.0" has unmet peer dependency "eslint@^4.9.0".
warning " > eslint-plugin-jsx-a11y@6.0.2" has unmet peer dependency "eslint@^3 ||^4".
warning " > eslint-plugin-react@7.5.1" has unmet peer dependency "eslint@^3.0.0 || ^4.0.0".
[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 3.98s.

[MikeTheCanuck]

Per #92 putting in place the correct versions of the peer Dependencies reduced this to a single spurious warning that makes no sense on the face of it:

warning " > eslint-config-airbnb@16.1.0" has unmet peer dependency "eslint-plugin-react@^7.4.0".

Makes no sense because that exact package and version is a member of the devDependencies section of the package.json right alongside eslint-config-airbnb@16.1.0:

  "devDependencies": {
    "eslint": "4.9.0",
    "eslint-config-airbnb": "^16.1.0",
    "eslint-plugin-import": "2.7.0",
    "eslint-plugin-jsx-a11y": "^6.0.2",
    "eslint-plugin-react": "7.4.0"
  }

[adam187]

@MikeTheCanuck I have same issue in my project. It looks like yarn bug, should be resolved in 1.4.0 yarnpkg/yarn#5088