Mixed `type` imports does not trigger `import/no-duplicates`

Description

import { useEffect } from "react";
import { useState } from "react";

import { type ComponentProps, useEffect } from "react";
import { useState } from "react";

import { type ComponentProps, useEffect, useState } from "react";

Contributor guide

Tech stack

javascripttypescript

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.

fresh

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

clear

Prerequisites

Basic ESLint plugin knowledgeUnderstanding of TypeScript type imports

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

75

Research direction

Investigate the `import/no duplicates` rule implementation in the repository, likely in `src/rules/no duplicates.js`. Understand how imports are currently parsed and duplicates detected. The fix should treat mixed type and value imports from the same module as duplicates. Look at existing tests to understand the expected behavior and add a test case for mixed imports. Review any related comments in the issue for additional context.