jsx-eslint/eslint-plugin-react

[Bug]: Not working with @typescript-eslint/parser v8

Open

#3,792 创建于 2024年8月1日

在 GitHub 查看
 (4 评论) (7 反应) (0 负责人)JavaScript (8,630 star) (2,797 fork)batch import
help wantedtypescript

描述

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

Due to : https://github.com/typescript-eslint/typescript-eslint/pull/8933

accessing "typeParameters" will now be undefined.

It needs to be changed to "typeArguments" (and the other deprecations in the Pr linked above).

Expected Behavior

The result is that eslint-pugin-react doesn't find any declared props in a typescript project.

I see there is a PR to fix this: https://github.com/jsx-eslint/eslint-plugin-react/pull/3788 but it is about the deprecations, not the fact that eslint-plugin-react just stops working without any indication why (no errors from npm etc.)

eslint-plugin-react version

7.35.0

eslint version

v8.57.0

node version

v22

贡献者指南

技术栈
typescriptjavascriptreactnodejs
领域
frontendtooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaScriptReactTypeScriptESLint plugin basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
The issue is caused by a breaking change in @typescript eslint/parser v8 where 'typeParameters' was renamed to 'typeArguments'. The fix involves finding all usages of 'typeParameters' in the eslint plugin react codebase (e.g., in rule implementations) and replacing them with 'typeArguments'. The linked PR #3788 addresses other deprecations but not this specific breakage, so a new PR should focus solely on this rename. After making changes, test with @typescript eslint/parser v8 to ensure the plugin works again. Consult the repository's contributing guidelines and existing tests for integration.