import-js/eslint-plugin-import

[import/no-unresolved]: Do not report properly configured self resolution

Open

#1,649 创建于 2020年2月8日

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

描述

In one of my modules I decided to use self resolution from testing as this helps to verify that my exports is setup and pointing to the correct file. My package.json contains "exports": "./index.js" and import lib from 'my-pkg-name'; works but import/no-unresolved reports this as an error.

For now I've added // eslint-disable-next-line import/no-unresolved but it would be nice to avoid this.

贡献者指南

技术栈
javascriptnodejs
领域
tooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of Node.js module resolutionFamiliarity with ESLint plugin developmentKnowledge of package.json exports field
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
Investigate the no unresolved rule implementation in src/rules/no unresolved.js. Understand how the rule currently resolves imports and whether it checks the package.json exports field. Consider modifying the resolver to recognize self referencing via exports. Look at existing tests for the rule to ensure any changes pass.