import-js/eslint-plugin-import

'import/parsers' setting breaks my editor linter (VS Code)

Open

#2,752 opened on Mar 30, 2023

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

Repository metrics

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

Description

Hi Friends,

I am trying to use the rule 'import/no-unused-modules': [2, { unusedExports: true }] which, from research, requires the following eslintrc config:

  settings: {
    'import/parsers': {
      '@typescript-eslint/parser': ['.ts', '.tsx'],
    },
    'import/resolver': {
      node: true,
      typescript: true,
    },
  },

However, when I add the 'import/parsers' setting, the editor lint plugin seems to stops reporting anything. Does anyone know what the cause for this is, and how to resolve it? This is the lint plugin log:

[Info  - 15:46:02] ESLint server is starting.
[Info  - 15:46:02] ESLint server running in node v16.14.2
[Info  - 15:46:02] ESLint server is running.
[Info  - 15:46:03] ESLint library loaded from: [...]/src/ui/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/api.js
[Warn  - 15:46:04] 
No ESLint configuration (e.g .eslintrc) found for file: [...]/src/ui/apps/webtrader/.eslintrc.js
File will not be validated. Consider running 'eslint --init' in the workspace folder ui
Alternatively you can disable ESLint by executing the 'Disable ESLint' command.

Contributor guide

Research direction
Examine how the 'import/parsers' setting is processed in eslint plugin import, particularly how it overrides default parser detection and causes ESLint to fail in VS Code. Look at the source code in 'lib/core/parse.js' and the settings handling. Check if the setting is interfering with the VS Code ESLint extension's file validation.
Tech stack
javascripttypescriptnodejs
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.
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.
Mostly clear
Prerequisites
JavaScriptESLintGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60