import-js/eslint-plugin-import

'no-unresolved' always additionally causes false positive 'extensions'

Open

#2,153 opened on Jul 15, 2021

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

Description

This is more of a low-priority FYI, given that no-unresolved always gets fixed right away, so the issue is inconsequential.

image

I haven't specified import/extensions rule and thus the default "never" should be in effect.
That's how it behaves, except when there's an actual (legitimate) issue with import resolution.

From .eslintrc:

"parser": "@babel/eslint-parser",
"extends": "airbnb",
...
"import/no-named-as-default": 1,
"import/order": "off",
"import/prefer-default-export": "off",

From devDependencies:

"@babel/eslint-parser": "^7.14.7",
"eslint": "^7.30.0",
"eslint-config-airbnb": "^18.2.1",
"eslint-import-resolver-webpack": "^0.13.1",
"eslint-loader": "^4.0.2",
"eslint-plugin-import": "^2.23.4",
"eslint-plugin-react": "^7.24.0",

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetoolingbackend
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
ESLint configurationeslint plugin import basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the 'no unresolved' rule source in eslint plugin import (likely in rules/no unresolved.js). Reproduce the issue using the provided .eslintrc and package.json setup. Identify how 'no unresolved' triggers a false positive for 'import/extensions' when resolution fails, and consider a fix that scopes the false warning only to actual unresolved paths.