import-js / import-js/eslint-plugin-import
import/named does not report non-existent exports in yarn workspace
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/jd2rogers2/eslint-plugin-import-bug-minimal-repo for testing it for yourself
as seen above, no report for `import/named` despite not having an `helloFooV2` export from `foo/index.js`
`foo` and `bar` are both separate workspaces, `bar` lists `foo` as a dependency, and foo is in `node_modules`
i would expect it to report
maybe a larger issue as there is also https://github.com/benmosher/eslint-plugin-import/issues/1832
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
Reproduce the missing report with the linked eslint-plugin-import-bug-minimal-repo, focusing on import/named and the foo/index.js export used by the separate yarn workspaces. Check how the foo dependency is resolved from node_modules and compare that behavior with the expected nonexistent helloFooV2 export report. Done means the rule reports the missing export in this workspace setup without regressing existing cases.
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
- 35/100