Create a basic app via 'yarn create react-app my-app --typescript' generates two warnings during initial installation:
warning "react-scripts > @typescript-eslint/[email protected]" has incorrect peer dependency "eslint@^5.0.0".
warning "react-scripts > @typescript-eslint/[email protected]" has incorrect peer dependency "eslint@^5.0.0".
No. This is a brand new repository with a brand new app created using brand new versions of yarn, create-react-app, and npm.
I found references to several "unmet peer dependency" warning issues, but nothing specifically about "incorrect peer dependency" warnings
Environment Info:
System:
OS: macOS 10.14.6
CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
Binaries:
Node: 12.8.0 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.10.3 - /usr/local/bin/npm
Browsers:
Chrome: 76.0.3809.100
Firefox: Not Found
Safari: 12.1.2
npmPackages:
react: ^16.9.0 => 16.9.0
react-dom: ^16.9.0 => 16.9.0
react-scripts: 3.1.1 => 3.1.1
npmGlobalPackages:
create-react-app: Not Found
(Write your steps here:)
No warnings
Warnings:
[3/4] 馃敆 Linking dependencies...
warning "react-scripts > @typescript-eslint/[email protected]" has incorrect peer dependency "eslint@^5.0.0".
warning "react-scripts > @typescript-eslint/[email protected]" has incorrect peer dependency "eslint@^5.0.0".
Should be reproducible in any similar dev environment, unless there is something specifically wrong with my setup.
Kindly bump up versions to latest one (currently 2.0.0 for both eslint-plugin & parser)
These warnings are generated on every installation/upgrade.
you guys should update these dependencies.
Updating eslint-plugin to 2.0.0 is a breaking change so we can't do that until at least the 3.2 release.
waiting for support for @typescript-eslint 2
Couldn't we pin ESLint's version to 5 so the peer dependency is met?
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
This seems to have been fixed for me
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
@allenmiller please close this issue
Appears to be fixed.
Most helpful comment
Updating
eslint-pluginto 2.0.0 is a breaking change so we can't do that until at least the 3.2 release.