import-js/eslint-plugin-import
'no-unresolved' always additionally causes false positive 'extensions'
Open
#2,153 opened on Jul 15, 2021
enhancementhelp wanted
Repository metrics
- Stars
- (5,940 stars)
- PR merge metrics
- (PR metrics pending)
Description
This is more of a low-priority FYI, given that no-unresolved always gets fixed right away, so the issue is inconsequential.
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",