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.