import-js/eslint-plugin-import

[import/no-unresolved]: Do not report properly configured self resolution

Open

#1,649 opened on Feb 8, 2020

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

Repository metrics

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

Description

In one of my modules I decided to use self resolution from testing as this helps to verify that my exports is setup and pointing to the correct file. My package.json contains "exports": "./index.js" and import lib from 'my-pkg-name'; works but import/no-unresolved reports this as an error.

For now I've added // eslint-disable-next-line import/no-unresolved but it would be nice to avoid this.

Contributor guide

Research direction
Examine the import/no unresolved rule's resolver to understand how it handles package self references via `exports` field. Look at existing tests and the resolver's logic for resolving module paths when the import source matches the package name.
Tech stack
javascriptnodejs
Domain
developer experiencetooling
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.
Clear
Prerequisites
Node.jsnpmESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65