import-js/eslint-plugin-import

import/named: wildcard export not working?

Open

#920 建立於 2017年8月23日

在 GitHub 查看
 (9 留言) (28 反應) (0 負責人)JavaScript (4,946 star) (1,540 fork)batch import
bughelp wanted

描述

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…

貢獻者指南

技術棧
javascriptnodejs
領域
toolingdeveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaScriptESLintNode.js module system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
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.
import/named: wildcard export not working? · import-js/eslint-plugin-import#920 | Good First Issue