[BUG] `npm outdated` no longer respects semver range for `npm:` style indirect versions

[ehoogeveen-medweb]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

With npm 10.8.1, npm outdated shows a different major version in the "Wanted" column even though the dependency uses a caret or tilde range.

Expected Behavior

npm outdated only shows minor and patch version bumps in the "Wanted" column (or only patch versions for a tilde range). This was the behavior on npm 10.8.0 and earlier.

Steps To Reproduce

1. Create an empty directory
2. Run npm init -y
3. Run npm install punycode-v1@npm:punycode@1.4.1 to install punycode version 1 with an alias.
4. Run npm outdated
5. Observe that punycode 2.3.1 is displayed in the Wanted column, even though this is a different major version.

Environment

• npm: 10.8.1
• Node.js: v20.4.0
• OS Name: Windows 11

[ehoogeveen-medweb]

Any idea when we might see a release with this fix? It's been 3 weeks now.