-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Closed
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusionbugESLint is working incorrectlyESLint is working incorrectlyrepro:yesIssues with a reproducible exampleIssues with a reproducible exampleruleRelates to ESLint's core rulesRelates to ESLint's core rules
Description
Environment
Node version: 22
npm version:
Local ESLint version: 9.30.0
Global ESLint version:
Operating System: Win11
What parser are you using?
@typescript-eslint/parser
What did you do?
Configuration
{
"rules": {
"no-duplicate-imports": "error"
}
}
import type A from "a";
import type { B } from "a";
What did you expect to happen?
Code passes
What actually happened?
Code triggers "no-duplicate-imports"
Link to Minimal Reproducible Example
Participation
- I am willing to submit a pull request for this issue.
Additional comments
In difference to value imports, TypeScript does not allow to combine default and named type imports, i.e. these are all syntax errors:
import type A, { B } from "a";
import type A, type { B } from "a";
import type A, { type B } from "a";
Metadata
Metadata
Assignees
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusionbugESLint is working incorrectlyESLint is working incorrectlyrepro:yesIssues with a reproducible exampleIssues with a reproducible exampleruleRelates to ESLint's core rulesRelates to ESLint's core rules
Type
Projects
Status
Complete