import-js/eslint-plugin-import

import/no-self-import incorrectly identifies self.

Open

#1,247 建立於 2018年12月18日

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

描述

The issue seems to be when you have a local directory that has the same name as a global import. For example, I have a project that uses redis, and the code that uses it sits in a redis directory.

e.g. File: redis/index.js

const redis = require('redis'); // <-- import/no-self-import error here

貢獻者指南

技術棧
javascriptnodejs
領域
developer experiencetooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of ESLint plugin developmentNode.js module resolution
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the rule implementation in the eslint plugin import repository, likely in src/rules/no self import.js. Understand how the rule currently determines if an import is a self import. The issue occurs when a local directory has the same name as a global package (e.g., 'redis'). The rule should differentiate based on whether the import resolves to the local file or the node modules package. Check existing test cases in tests/src/rules/no self import.js. Look at the module resolution logic (e.g., using eslint module utils/resolve). Consider adding a check to see if the resolved path is within the same project directory.
import/no-self-import incorrectly identifies self. · import-js/eslint-plugin-import#1247 | Good First Issue