import-js/eslint-plugin-import

import/named does not report non-existent exports in yarn workspace

Open

#2,005 建立於 2021年3月12日

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

描述

Screen Shot 2021-03-12 at 9 45 07 AM

https://github.com/jd2rogers2/eslint-plugin-import-bug-minimal-repo for testing it for yourself

as seen above, no report for import/named despite not having an helloFooV2 export from foo/index.js foo and bar are both separate workspaces, bar lists foo as a dependency, and foo is in node_modules
i would expect it to report maybe a larger issue as there is also https://github.com/benmosher/eslint-plugin-import/issues/1832

貢獻者指南

技術棧
javascriptnodejs
領域
developer experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of ESLint pluginsKnowledge of yarn workspacesFamiliarity with Node.js module resolution
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the minimal reproduction repository at https://github.com/jd2rogers2/eslint plugin import bug minimal repo to understand the workspace structure. Examine the `import/named` rule implementation in the plugin's source code, focusing on how it resolves named exports from dependencies in a workspace context. Check if the issue is related to the module resolver not properly handling symlinked workspaces. Also review related issue #1832 for additional context. Consider writing a test case that replicates the scenario and verify if the bug is still present with the latest version of the plugin.