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.