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 (1,540 forks)batch import
bughelp wanted

Repository metrics

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

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

Research direction
Investigate the import/named rule logic for resolving wildcard exports. Trace the path from `export *` to the source module and check why the export is not found.
Tech stack
javascriptnodejs
Domain
developer experiencetooling
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
JavaScriptNode.jsESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30