Skip to content
This repository was archived by the owner on Jun 11, 2020. It is now read-only.
This repository was archived by the owner on Jun 11, 2020. It is now read-only.

Scoped & versioned packages can't pass path mappings checks #506

Description

In DefinitelyTyped/DefinitelyTyped#29979, I was trying to create a new major version of a scoped package. In order to do that, you're supposed to add a path mapping similar to the example in the DefinitelyTyped readme:

        "paths": {
            "history": [ "history/v2" ]
        },

For the package I was trying to update, I believe that'd be:

        "paths": {
            "@expo/vector-icons": [ "expo__vector-icons/v6" ]
        },

However, the code here doesn't strip the version info and enforces that the mapping match the dependency name once unmangled. This means I'd have to write something like the following (which is incorrect):

        "paths": {
            "@expo/vector-icons": [ "expo__vector-icons" ]
        },

Would a PR be accepted to change this behavior?

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