import-js/eslint-plugin-import

[import/extensions] ".." and "." import paths are incorrectly flagged as requiring an extension, when either is al local package

Open

#2,844 opened on Jul 31, 2023

View on GitHubContributor guide
 (2 comments) (2 reactions) (0 assignees)JavaScript (1,548 forks)batch import
bughelp wanted

Repository metrics

Stars
 (5,940 stars)
PR merge metrics
 (PR metrics pending)

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
Investigate the import resolution logic for '.' and '..' paths when the package has a local package.json. Trace through the code that handles extensions and check how it determines if a path is a local package.
Tech stack
javascript
Domain
devtools
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptNode.jsESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70