import-js/eslint-plugin-import

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

Open

#1,810 创建于 2020年6月8日

在 GitHub 查看
 (73 评论) (86 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)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
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
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.