import-js/eslint-plugin-import

`no-unresolved` is not aware of `exports` definition in `package.json`

Open

#1,810 opened on 2020年6月8日

GitHub で見る
 (73 comments) (86 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
`exports` supporthelp wanted

説明

From this announcement

Package entry points and the package.json “exports” field

There are now two fields that can define entry points for a package: “main” and“exports”. The “main” field is supported in all versions of Node.js, but its capabilities are limited: it only defines the main entry point of the package. A new package.json field “exports” can also define the main entry point, along with subpaths. It also provides encapsulation, where only the paths explicitly defined in “exports” are available for importing. “exports” applies to both CommonJS and ES module packages, whether used via require or import.

Might need to be fix in resolve package..

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

技術スタック
javascriptnodejs
領域
developer experiencetoolingbackend
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
3-5 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Node.js module resolutionESLint plugin developmentUnderstanding of package.json exports field
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
45
調査方針
Investigate the current resolution logic in the `resolve` package, specifically the PR #224 which adds support for the `exports` field. Then, integrate that support into the `no unresolved` rule in eslint plugin import. Check the rule's source code at `src/rules/no unresolved.js` and understand how it calls the resolver. Also review the issue comments for proposed solutions.