import-js/eslint-plugin-import

Doesn't differentiate between `module-name` and `@namespace/module-name`

Open

#1,747 opened on May 4, 2020

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

Repository metrics

Stars
 (5,940 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

Description

I'm working in a monorepo with a package named @arc/dotenv which requires dotenv. This triggers import/no-self-import. My suspicion is that it's not taking the namespace into account. Another possibility: the package lives at <root>/tools/dotenv, so perhaps the issue comes up after the module gets resolved?

Contributor guide

Research direction
Investigate how the `import/no self import` rule resolves module names, especially for scoped packages like `@namespace/module name`. Check if the rule properly strips the namespace before comparing with the package name. Also consider the file path resolution logic based on the package location relative to the project root.
Tech stack
javascript
Domain
tooling
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
JavaScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70