[no-duplicates] incorrect report on two non-combinable ts type import statements

Description

import type ESLint from 'eslint'
import type { Linter, SourceCode } from 'eslint'

import type ESLint, { Linter, SourceCode } from 'eslint'

packages/eslint-plugin-mdx/src/processors/options.ts:5:8 - error TS1363: A type-only import can specify a default import or named bindings, but not both.

5 import type ESLint, { Linter, SourceCode } from 'eslint'

Contributor guide

Tech stack

javascripttypescriptnodejs

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.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

TypeScript type importsESLint rule testingno duplicates rule implementation

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70

Research direction

The bug is in the no duplicates rule. When TypeScript type imports combine a default import with named imports, they cannot be merged. The rule should detect this and not report a duplicate. Look at the rule implementation in the repository, likely in rules/no duplicates.js. Consider adding a check for TypeScript type only imports to avoid false positive.