Skip to content

PATTERN_KEY_COMPARE algorithm should be updated #46050

Description

@unional

Version

19.3.1

Platform

all

Subsystem

No response

What steps will reproduce the bug?

https://nodejs.org/api/esm.html#resolver-algorithm-specification

The assertions: Assert: keyA ends with "/" or contains only a single "*".

is no longer correct as ESM supports file extensions, e.g.:

  • #a/b.js
  • ./foo/*.js

I have released pattern-key-compare for resolve.imports.

How often does it reproduce? Is there a required condition?

N/A

What is the expected behavior?

The spec should be adjusted.

Also, should expect only single * instead of allowing multiple *. But that's a breaking change.

What do you see instead?

N/A

Additional information

No response

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions