eslint(import/named) reports `not found` errors in 2.30.0

描述

import Select, { ClearIndicatorProps, GroupBase, OptionProps, Props, createFilter } from 'react-select';
Error:   2:18  error  ClearIndicatorProps not found in 'react-select'  import/named
Error:   2:39  error  GroupBase not found in 'react-select'            import/named
Error:   2:50  error  OptionProps not found in 'react-select'          import/named
Error:   2:63  error  Props not found in 'react-select'                import/named

import { DocumentNode } from 'graphql';
Error:   5:10  error  DocumentNode not found in 'graphql'  import/named

贡献者指南

技术栈

javascript

领域

developer experience

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-3 hours

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

active

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

ESLintJavaScriptimport resolution

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

75

研究方向

Investigate the Git diff between version 2.29.1 and 2.30.0 to identify the change that introduced the regression. Focus on the `rules/named.js` file, which implements the `import/named` rule. Check the export resolution logic, especially how it handles type only exports or named exports from packages that re export types (e.g., react select, graphql). Review the release notes and any related PRs mentioned in the issue comments for additional context.