import-js/eslint-plugin-import

import/named: wildcard export not working?

Open

#920 opened on Aug 23, 2017

View on GitHub
 (9 comments) (28 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
bughelp wanted

Description

Simplified version: a.js:

    export const a = 5

b.js:

    export * from './a'

c.js:

    import {a} from './b'

c.js errors with import/named: export a not found in b.js

however, when I try this simplified version, there is no error for c but it also doesn't error if I import x which definitely doesn't exist. So not sure what is going on…

Contributor guide

Tech stack
javascriptnodejs
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.
1-2 days
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.
mostly clear
Prerequisites
JavaScriptESLintNode.js module system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the import/named rule in src/rules/named.js and the underlying export resolution logic. Check the test suite for existing wildcard export test cases. Attempt to create a minimal reproducible example that consistently triggers the error. Review issue comments for additional context or potential fixes.