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.
Doesn't differentiate between `module-name` and `@namespace/module-name` · import-js/eslint-plugin-import#1747 | Good First Issue