Namespaced exports reported as duplicate identifiers

Description

// AB.ts
export type A = {};
export type B = {};

// ABFeature.ts
export type * as AB from "./AB.ts";

// foo.ts
export type A = {};

// index.ts
export * from "ABFeature.ts"; // Error: duplicate identifier `A`
export * from "foo.ts";       // Error: duplicate identifier `A`

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

JavaScript importsTypeScript namespaced exportsESLint rule development

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

55

Research direction

Investigate the eslint plugin import rule that reports duplicate identifiers (likely the 'no duplicates' rule). The issue shows that namespaced re exports are incorrectly flagged. The rule's logic for detecting duplicates needs to account for namespaced exports (e.g., `export type * as AB from './AB.ts'`), which do not expose the inner symbols directly. Look at the rule implementation in the repository's source code (e.g., `rules/no duplicates.js`) and understand how exports are resolved. The fix likely involves filtering out namespaced re exports when checking for duplicates. Comment on the issue to confirm the expected behavior and discuss potential approach.