import-js/eslint-plugin-import

Doesn't differentiate between `module-name` and `@namespace/module-name`

Open

#1,747 创建于 2020年5月4日

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

描述

I'm working in a monorepo with a package named @arc/dotenv which requires dotenv. This triggers import/no-self-import. My suspicion is that it's not taking the namespace into account. Another possibility: the package lives at <root>/tools/dotenv, so perhaps the issue comes up after the module gets resolved?

贡献者指南

技术栈
javascriptnodejs
领域
toolingdeveloper experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
ESLint plugin developmentmodule resolution
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the `no self import` rule in `src/rules/no self import.js` to understand how it matches module names. Check if it uses `resolve` to resolve the module path and if it correctly handles scoped package names (e.g., `@arc/dotenv`). Look at the resolver logic for monorepo setups and verify whether the scope is stripped during comparison.