Skip to content

doc: confusing support for extensionless ESM #30655

Closed
@azz

Description

From the ESM docs (emphasis mine):

import statements of .js and extensionless files are treated as ES modules if the nearest parent package.json contains "type": "module".

Unless I am mistaken (discussed in nodejs/modules#443), extensionless module resolution is not currently supported.

How can you have an import statement for an extensionless file when it does not resolve?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    esmIssues and PRs related to the ECMAScript Modules implementation.experimentalIssues and PRs related to experimental features.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions