import-js/eslint-plugin-import

Support for checking `require.resolve()`

Open

#585 建立於 2016年9月25日

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

描述

Sometimes I use require.resolve() just to resolve paths to other resources than javascript modules.

Okay, this is not a regular import, but it would be nice if this plugin could also check these paths.

Maybe it could be a new setting like 'import/check-require-resolve': true, whereas various rules related to CommonJS imports also apply here.

貢獻者指南

技術棧
javascriptnodejs
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptNode.js require.resolve()ESLint plugin developmenteslint plugin import structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Examine how the plugin currently handles `require()` calls, particularly in rules like `no unresolved` and `no extraneous dependencies`. Identify where `require.resolve` is used as an expression and consider extending the AST visitor to detect `CallExpression` with callee `require.resolve`. Introduce a configuration option, e.g., `'import/check require resolve': true`, and apply the same import validation logic to the arguments of `require.resolve()`.