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 (4,946 stars) (1,540 forks)batch import
enhancementhelp wanted

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

Tech stack
javascriptnodejs
Domain
tooling
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Node.js module resolutionFamiliarity with ESLint plugin developmentKnowledge of package.json exports field
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the no unresolved rule implementation in src/rules/no unresolved.js. Understand how the rule currently resolves imports and whether it checks the package.json exports field. Consider modifying the resolver to recognize self referencing via exports. Look at existing tests for the rule to ensure any changes pass.