Widen eslint-config-react-app peer dependency versions

[lukyth]

Close#7759

Description

From #7759, install eslint-config-react-app will produce a warning:

warning " > eslint-config-react-app@5.0.2" has incorrect peer dependency "eslint-plugin-flowtype@3.x".
warning " > eslint-config-react-app@5.0.2" has incorrect peer dependency "eslint-plugin-react-hooks@1.x".

They will be fixed by widening the peer dependency values for eslint-plugin-flowtype and eslint-plugin-react-hooks to include the latest major.

Acceptance criteria

• eslint-plugin-flowtype in this repo should be 3.x || 4.x.
• eslint-plugin-react-hooks in this repo should be 1.x || 2.x.
• Installing eslint-config-react-app should not produce the warning above.

[ianschmitz]

I don't think we can roll out the eslint-plugin-react-hooks update without a major release of react-scripts. For example this will cause a linter warning with eslint-plugin-react-hooks@2.x:

import{useBasename}from'history'useBasename();

You could work around it like so:

import{useBasenameaswithBasename}from'history'withBasename();

but this would still be a breaking change for existing apps.

[lukyth]

Is it possible to roll out a new major for this? Calling a hook at top level is potentially a bug anyway so I think it's a good idea to allow create-react-app's user to have access to this rule as soon as possible.

[ianschmitz]

Thanks! I updated the PR to focus on the flow plugin fix. The hooks plugin peer dependency is currently correct as we use version 1.7.0 in react-scripts, but will be addressing in #8505.

[ianschmitz]

I decided to include the hooks peer dependency change as well, but we won't bump the actual plugin version here and will instead do it in next major of CRA. Sorry for the back and forth.

[ianschmitz]

Thanks!