Renovate does not recognize PNPM aliases

[jonkoops]

What would you like help with?

I think I found a bug

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

It seems that Renovate does not support PNPM aliases, specifically our project aliases the following dependency for backwards compatibility:

package.json

{
  "dependencies": {
    "@patternfly-v5/patternfly": "npm:@patternfly/patternfly@^5.2.0"
  }
}

It seems that Renovate mis-identifies the dependency and instead attempts to resolve @patternfly-v5/patternfly directly on the NPM registry, for more information see attached logs, or this example PR.

Logs (if relevant)

Logs

Scope: all 8 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 74, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/jonkoops/keycloak/themes/src/main/resources/theme/keycloak/common/resources:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@patternfly-v5%2Fpatternfly: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/jonkoops/keycloak/themes/src/main/resources/theme/keycloak/common/resources

@patternfly-v5/patternfly is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

To get started, please read our guide on creating a minimal reproduction.

Good luck,

The Renovate team

[jonkoops]

I've set up a repository to test this problem in isolation. Seems that there dependency updates do work (see jonkoops/pnpm-repro#2), but an update for my aliased dependency is never offered, even if it is out of date.

[rarkins]

Converted to issue: #28541