import-js/eslint-plugin-import
Voir sur GitHub`no-unresolved` is not aware of `exports` definition in `package.json`
Open
#1 810 ouverte le 8 juin 2020
`exports` supporthelp wanted
Métriques du dépôt
- Stars
- (4 946 stars)
- Métriques de merge PR
- (Merge moyen 138j 22h) (3 PRs mergées en 30 j)
Description
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..