import-js / import-js/eslint-plugin-import
import/named: wildcard export not working?
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
Simplified version:
a.js:
```
export const a = 5
```
b.js:
```
export * from './a'
```
c.js:
```
import {a} from './b'
```
c.js errors with `import/named: export a not found in b.js`
however, when I try this simplified version, there is no error for c but it also doesn't error if I import `x` which definitely doesn't exist. So not sure what is going on…
Contributor guide
Research direction
Start with the a.js, b.js, and c.js reproductions and the import/named rule behavior described in the issue. Run both simplified examples through ESLint, then inspect how wildcard exports are handled. Done means the valid import of a is accepted while an import of nonexistent x is reported consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100