import-js/eslint-plugin-import

`no-extraneous-dependencies` doesn't support nested package.json

Open

#1,913 opened on 2020年9月29日

GitHub で見る
 (7 comments) (12 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
enhancementhelp wanted

説明

With Node’s ES Module support explicitly suggesting to use multiple package.json files in subfolders, I think no-extraneous-dependencies should automatically support nested package.json without further config

The nearest parent package.json is defined as the first package.json found when searching in the current folder, that folder’s parent, and so on up until the root of the volume is reached.

I know that no-extraneous-dependencies has options to manually specify each folder, but I think that this could be done automatically.

コントリビューターガイド

技術スタック
javascriptnodejs
領域
developer experiencetooling
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Understanding of ESLint plugin architectureFamiliarity with Node.js module resolution
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
55
調査方針
Examine the current implementation of `no extraneous dependencies` rule in the eslint plugin import repository (likely in `src/rules/no extraneous dependencies.js`). Understand how it currently resolves package.json files and how it uses options for custom folder paths. Implement automatic detection by searching for the nearest parent package.json from each file's directory, as per Node.js resolution algorithm, without requiring explicit configuration. Check if there are any existing PRs or discussions related to this feature.