pnpm outdated command fails to detect updates when registry is configured

[jiadesen]

pnpm version

7.13.4

Code to reproduce the issue:

NA

Expected behavior:

Actual behavior:

Additional information:

• node -v prints: v16.16.0
• Windows, macOS, or Linux?: macOS

[zkochan]

A workaround is to set the registry to:

registry=https://registry.npmmirror.com

The issue is that the code exits here:

pnpm/packages/outdated/src/outdated.ts

Lines 97 to 111 in 51e5a87

	// It might be not the best solution to check for pkgSnapshot.name
	// TODO: add some other field to distinct packages not from the registry
	if (pkgSnapshot.resolution && (pkgSnapshot.resolution['type'] || pkgSnapshot.name)) {
	if (current !== wanted) {
	outdated.push({
	alias,
	belongsTo: depType,
	current,
	latestManifest: undefined,
	packageName,
	wanted,
	})
	}
	return
	}

and that happens because the domain of the configured registry differs from the domain that hosts the tarball. Even though https://registry.npm.taobao.org just redirects to https://registry.npmmirror.com