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