import-js / import-js/eslint-plugin-import
Better error message for `exports`-only packages
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
I have seen in several places here (#2293, #2331, https://github.com/import-js/eslint-plugin-import/issues/2319#issuecomment-988013712) that the support for `exports`-only dependencies is missing, and might not be added. The error message `Unable to resolve path to module 'got'.` does not do a good job to explain that. Would it be possible to handle this case better by providing a custom error message?
It would also be nice to have the project’s position on such dependencies to be explicitly stated somewhere in readme, or the support for it tracked in some "official" issue.
Contributor guide
Research direction
Start by reviewing the linked issues and the current handling of the `Unable to resolve path to module` error for `exports`-only dependencies. Determine where that message is produced and check whether existing tests cover this dependency case. Done means the failure explains the `exports`-only situation and the project's position or support status is documented or officially tracked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100