import-js/eslint-plugin-import

Differences between eslint CLI and vscode linting

Open

#3180 opened on Apr 22, 2025

View on GitHub
 (11 comments) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
help wanted

Description

Hello!

I've upgraded to eslint@9 in my project and have some issues with linting.

Linting of import/order errors is different in CLI/vscode.

What i'm getting in vscode:

Image

what i have in terminal:

Image

Maybe it's caused by several eslint configs or aliases, but i think i'm using all needed settings for this.

I've made repo with reproduction of this problem: https://github.com/chelentos/vscode-eslint-repr

There are vscode settings in README.

Configs for eslint you can find here: https://github.com/gravity-ui/eslint-config Import/order config: https://github.com/gravity-ui/eslint-config/blob/main/import-order.js

I've already created issue in vscode plugin repo, but maybe you can help me too.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingdeveloper experience
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.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of ESLint configurationUnderstanding of import ordering rules
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Start by examining the provided reproduction repository at https://github.com/chelentos/vscode eslint repr and the referenced VSCode issue at https://github.com/microsoft/vscode eslint/issues/2006. Compare the ESLint configurations used in the CLI (e.g., .eslintrc files) versus the VSCode extension settings. Look for differences in how the import/order rule is parsed or applied, particularly focusing on the merge behavior of multiple configs. Check the eslint plugin import source in the repository to see if there are any known issues with flat config compatibility or specific rule options that might cause different behavior.