import-js / import-js/eslint-plugin-import
[import/extensions] ".." and "." import paths are incorrectly flagged as requiring an extension, when either is al local package
Open
bug
help wanted
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
In #2778, we determined that this plugin incorrectly flags ".." and "." import paths, when those imports refer to a local package (with a package.json).
Contributor guide
Research direction
Start with the import/extensions rule and read issue #2778 for the prior discussion. Reproduce the case where ".." or "." resolves to a local package with a package.json, then verify that the rule no longer incorrectly requires an extension for those imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100