Skip to content

pnpm why does not list packages which are aliased via npm: protocol #8660

@eps1lon

Description

@eps1lon

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

9.12.2

Which area(s) of pnpm are affected? (leave empty if unsure)

CLI

Link to the code that reproduces this issue or a replay of the bug

https://github.com/eps1lon/pnpm-why-npm-alias

Reproduction steps

{
  "name": "pnpm-why-npm-alias",
  "dependencies": {
    "@types/react": "npm:[email protected]"
  },
  "packageManager": "[email protected]"
}
$ pnpm why @types/react

Describe the Bug

Output of pnpm why @types/react is empty

Expected Behavior

$ pnpm why @types/react
Legend: production dependency, optional only, dev only

dependencies:
@types/react npm:[email protected]

Which Node.js version are you using?

20.14.0

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions