**Do you want to request a *feature* or report a *bug*?**
feature

**What is the current behavior?**
Using in my `package.json`:
```
    "eslint": "^6.0.0",
    "eslint-plugin-react-hooks": "^1.6.0",
```
Yarn emits:
```
warning " > eslint-plugin-react-hooks@1.6.0" has incorrect peer dependency "eslint@^3.0.0 || ^4.0.0 || ^5.0.0".
```

**What is the expected behavior?**
No warning.

AFAICT, there shouldn't be other change needed besides updating the peer dependency version in the `package.json`: https://eslint.org/docs/user-guide/migrating-to-6.0.0
so it looks like I could just ignore the warning, but I'd rather be sure the plugin is actually compatible with ESLint 6.0.0

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
n/a
`,
    `
      // Currently valid because we don't check for hooks in classes.
      // See ClassComponentWithFeatureFlag for rationale.
      // We *could* make it invalid if we don't regress that false positive.
      class ClassComponentWithHook extends React.Component {
        render() {
          React.useState();
        }
      }
    `,
    `
      // Currently valid.
      // These are variations capturing the current heuristic--
      // we only allow hooks in PascalCase, useFoo functions,
      // or classes (due to common false positives and because they error anyway).
      // We *could* make some of these invalid.
      // They probably don't matter much.
      (class {useHook = () => { useState(); }});
      (class {useHook() { useState(); }});
      (class {h = () => { useState(); }});
      (class {i() { useState(); }});
    `,
    `
      // Currently valid although we *could* consider these invalid.
      // It doesn't make a lot of difference because it would crash early.
      use();
      _use();
      useState();
      _useState();