[no-duplicates] prefer-inline should merge type and non-type imports

Description

import { A } from "./mod";
import type { B } from "./mod";

import { A, type B } from "./mod";

Contributor guide

Tech stack

javascripttypescriptnodejs

Domain

developer experiencetooling

Issue type

feature

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 knowledge of ESLint plugin structureunderstanding of TypeScript import syntax

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

70

Research direction

Investigate the current implementation of the `prefer inline` rule in `src/rules/prefer inline.js`. The issue specifies that consecutive import statements from the same module (one type only, one value) should be merged into a single import with the `type` keyword used inline. Look at how the rule currently handles import declarations and identify where to add logic to detect and merge such imports. Check if there are existing tests in `tests/src/rules/prefer inline.js` and consider adding test cases for this scenario. The fix should only apply when the imports are side by side and from the same module.