Skip to content
New issue

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

[Bug]: typescript-eslint v6 deprecation warnings #3689

Closed
2 tasks done
thomasmarr opened this issue Feb 10, 2024 · 1 comment
Closed
2 tasks done

[Bug]: typescript-eslint v6 deprecation warnings #3689

thomasmarr opened this issue Feb 10, 2024 · 1 comment
Labels

Comments

@thomasmarr
Copy link

Is there an existing issue for this?

  • I have searched the existing issues and my issue is unique
  • My issue appears in the command-line and not only in the text editor

Description Overview

Latest recommended preset has a at least one rule that is using deprecated typeParameters property from typescript-eslint. See https://typescript-eslint.io/linting/troubleshooting/#the-key-property-is-deprecated-on-type-nodes-use-key-instead-warnings

When running tests I see hundreds of instances of "DeprecationWarning: The 'typeParameters' property is deprecated on CallExpression nodes. Use 'typeArguments' instead. See https://typescript-eslint.io/linting/troubleshooting#the-key-property-is-deprecated-on-type-nodes-use-key-instead-warnings." in console output.

If I remove "plugin:react/recommended" from the extends property of eslintConfig, the warnings are removed.

There's a fix described at the above link which keeps backward compat with v5 and looks pretty straightforward.

Expected Behavior

Expect no deprecation warnings.

eslint-plugin-react version

v7.33.2

eslint version

v8.56.0

node version

v20.10.0

@thomasmarr thomasmarr added the bug label Feb 10, 2024
@ljharb
Copy link
Member

ljharb commented Feb 10, 2024

Duplicate of #3602. Will be fixed by #3629.

@ljharb ljharb closed this as not planned Won't fix, can't repro, duplicate, stale Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants