import-js/eslint-plugin-import

import/named doesn't work when the target has no exports

Open

#1,147 创建于 2018年7月30日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)batch import
help wanted

描述

Given:

// a.js
console.log('This file has no exports')

// b.js
import { doesntExist } from './a'

I'd expect the import/named rule to show an error for doesntExist. It doesn't. What am I missing? Is there a way to check for this type of error?

贡献者指南

技术栈
javascriptnodejs
领域
toolingdeveloper experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaScriptESLint plugin developmentNode.js
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
Look at the rule implementation for `import/named` in the source tree, likely under `src/rules/named.js`. Examine the current logic that checks named exports and see where it fails when the module has no exports. Consider adding a test case for a module with no exports importing a non existent named export. Also check the resolver or module parsing to understand how exports are obtained.