We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We support eslint@9 but the peerDependencies do not include it. This causes npm import failure when using current npm versions.
eslint@9
peerDependencies
Steps to repro:
[email protected]
Expected: eslint-plugin-react install ok
Actual: eslint-plugin-react install fails with
npm ERR! Could not resolve dependency: npm ERR! peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8" from [email protected] npm ERR! node_modules/eslint-plugin-react npm ERR! dev eslint-plugin-react@"7.34.1" from the root project
Environment: node: v20.12.2 npm: 10.5.0
The fail will downgrade to a warning if npm legacy-peer-deps is used, but we should address the root cause.
eslint-plugin-react should install ok
v7.34.1
v9.0.0
v20.12.2
The text was updated successfully, but these errors were encountered:
Please wait to file PRs until a maintainer tells you it's desired. Your PR is a duplicate of #3726, and this issue is a duplicate of #3699.
Sorry, something went wrong.
No branches or pull requests
Is there an existing issue for this?
Description Overview
We support
eslint@9
but thepeerDependencies
do not include it. This causes npm import failure when using current npm versions.Steps to repro:
eslint@9
[email protected]
Expected:
eslint-plugin-react install ok
Actual:
eslint-plugin-react install fails with
Environment:
node: v20.12.2
npm: 10.5.0
The fail will downgrade to a warning if npm legacy-peer-deps is used, but we should address the root cause.
Expected Behavior
eslint-plugin-react should install ok
eslint-plugin-react version
v7.34.1
eslint version
v9.0.0
node version
v20.12.2
The text was updated successfully, but these errors were encountered: