import-js/eslint-plugin-import

import/no-self-import incorrectly identifies self.

Open

#1,247 opened on Dec 18, 2018

View on GitHub
 (4 comments) (1 reaction) (0 assignees)JavaScript (1,540 forks)batch import
bughelp wanted

Repository metrics

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

Description

The issue seems to be when you have a local directory that has the same name as a global import. For example, I have a project that uses redis, and the code that uses it sits in a redis directory.

e.g. File: redis/index.js

const redis = require('redis'); // <-- import/no-self-import error here

Contributor guide

Research direction
Investigate the import/no self import rule logic to understand how it resolves module paths and why it incorrectly flags a self import when a local directory shares a name with a global package. Look for the resolution algorithm and test cases.
Tech stack
javascript
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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.
Clear
Prerequisites
Node.jsESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65