import-js / import-js/eslint-plugin-import
eslint(import/named) reports `not found` errors in 2.30.0
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
After upgrading from 2.29.1 to 2.30.0 we got some not found errors from import/named rule
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
in both cases only imported interfaces are marked with error
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the import/named rule and reproduce the regression using the react-select and graphql interface-only imports described in the issue. Compare behavior between versions 2.29.1 and 2.30.0, then verify that valid imported interfaces no longer produce not found errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100