Open
Description
User story
As an engineer, I want only one ESLint rule to target a given issue, so that I only get one finding per issue and avoid unnecessary noise.
Acceptance criteria
There is only one rule for duplicate import.
Minimal reproduction of current behaviour
The no-duplicate-imports rule included here targets duplicate module import lines and aims to merge them.
The import/no-duplicates rule included from recommended config here seems to be an expanded version of that rule - it recognises type import as separate, allows for path variation for file formats.
Desired behaviour showcase
The vanilla no-duplicate-imports can be removed.
Which configuration is this related to?
default
ESLint version
No response