no-named-as-default-member rule is broken in specific cases

Repository metrics

Stars

5,940 stars (5,940 stars)

PR merge metrics

Avg merge 138d 22h (Avg merge 138d 22h)3 merged PRs in 30d (3 merged PRs in 30d)

Description

// id-values-map.js

const ID_VALUE_MAP = {
  x: 4,
  y: 14,
};

const DEFAULT_ID = 'x';

export default ID_VALUE_MAP;
export { DEFAULT_ID };

// usage.js

import ID_VALUE_MAP, { DEFAULT_ID } from './id-values-map';

use(ID_VALUE_MAP[DEFAULT_ID]);
// ESLint: Caution: `ID_VALUE_MAP` also has a named export `DEFAULT_ID`. Check if you meant to write `import {DEFAULT_ID} from './id-values-map'` instead.(import/no-named-as-default-member)

Contributor guide

Research direction

Inspect the rule no named as default member logic to understand why it incorrectly warns when a default export object has a property name that matches a named export. Check how the rule resolves export names and compare with the default export's properties.

Tech stack

javascript

Domain

tooling

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

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.

Active

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

Clear

Prerequisites

JavaScriptESLint

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

70