import-js/eslint-plugin-import

`export * as ns` false positive on import/named rule

Closed

#1,883 opened on Aug 17, 2020

View on GitHubContributor guide
 (3 comments) (12 reactions) (0 assignees)JavaScript (1,549 forks)batch import
bughelp wanted

Repository metrics

Stars
 (5,940 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

Description

// module1.js
export const hello = 'world';

// module2.js
export * as mod1 from './module1'

// module3.js
import { mod1 } from './module2'; // <-- getting "mod1 not found", triggered by `import/named` rule.

I can create a repro case if needed.

Contributor guide

Research direction
The issue is a false positive in the import/named rule when using `export * as ns` syntax. To fix, inspect the rule's logic in src/rules/named.js and handle the case where a namespace re export is used. Add a test case to reproduce the bug. Check issue comments and any existing PRs for additional guidance.
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.
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
JavaScriptESLintAST traversal
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55