import-js/eslint-plugin-import

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

Open

#1810 aperta il 8 giu 2020

Vedi su GitHub
 (73 commenti) (86 reazioni) (0 assegnatari)JavaScript (1540 fork)batch import
`exports` supporthelp wanted

Metriche repository

Star
 (4946 star)
Metriche merge PR
 (Merge medio 138g 22h) (3 PR mergiate in 30 g)

Descrizione

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..

Guida contributor