import-js/eslint-plugin-import
`no-unresolved` is not aware of `exports` definition in `package.json`
オープン
#1,810 opened on 2020/06/08
`exports` supporthelp wanted
Repository metrics
- Stars
- (5,939 個のスター)
- PR merge metrics
- (平均マージ 138d 22h) (30d で 3 merged PRs)
説明
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..