import-js / import-js/eslint-plugin-import
No longer resolves any dependency
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
The ESLint error is as follows for every single dependency in any of my JS/JSX files:
```
Unable to resolve path to module 'prop-types'. (eslint import/no-unresolved) ...
Unable to resolve path to module 'styled-components'. (eslint import/no-unresolved) ...
Unable to resolve path to module '../conf'. (eslint import/no-unresolved) ...
```
Downgrading to v0.13.4 fixes things for me. I have a fairly standard config, nothing specific defined/configured for the import plugin specifically.
I suspect it's something to do with the switch to `"resolve": "^2.0.0-next.4",`.
Possibly related: https://github.com/import-js/eslint-plugin-import/issues/2859
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 failure with the standard configuration against the affected version, using the reported JS/JSX imports such as prop-types, styled-components, and ../conf; compare it with v0.13.4. Read the resolver change to "resolve": "^2.0.0-next.4" and the related issue #2859. Done means dependencies resolve again without import/no-unresolved errors and the regression is covered by a test.
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
- Needs clarification
- Newbie friendliness
- 35/100