Skip to content

Replacing the built-in default import resolver that supports exports and imports from package.json #208

Closed
@SukkaW

Description

@SukkaW

eslint-plugin-import-x has eslint-import-resolver-node as a dependency. When no resolver is specified in the eslint config, the eslint-import-resolver-node will be used. However, eslint-import-resolver-node doesn't support exports and imports from package.json and @ljharb simply refuses doesn't have time to implement this feature and even locks the feature request issue, see import-js/eslint-plugin-import#1810.

So our plan is to abandon the eslint-import-resolver-node. We will be building a new eslint import resolver upon @dual-bundle/import-meta-resolve enhanced-resolve. We will ship it with eslint-plugin-import-x and it will be an interface v3-only resolver.

In the next major version of eslint-plugin-import-x, we will remove eslint-import-resolver-node in favor of our own default resolver.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions