[BUG] npm possibly installs wrong dependencies

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

Based on the discussion with the maintainer of the typescript-eslint project in the SR https://github.com/typescript-eslint/typescript-eslint/issues/8732, npm 10.5.0 wrongly resolves a dependency.

If you check the version listed in ./node_modules/@typescript-eslint/utils/package.json it should be v7
If it's v5 then double check ./node_modules/typescript-eslint - it should contain its own ./node_modules/@typescript-eslint/utils which is v7.
If you don't have a v7 version of the utils package - then that's the cause - npm is doing the wrong thing.

Expected Behavior

No response

Steps To Reproduce

Install:

{
	"name": "test",
	"type": "commonjs",
	"devDependencies": {
		"@eslint/js": "8.57.0",
		"cross-env": "7.0.3",
		"eslint": "8.57.0",
		"eslint-plugin-jest": "27.9.0",
		"typescript": "5.4.2",
		"typescript-eslint": "7.3.1"
	}
}

Environment

• npm: 10.5.0
• Node.js: 20.11.0
• OS Name: macOS
• System Model Name: Macbook Pro
• npm config:

//registry.npmjs.org/:_authToken = (protected)
audit = false
fund = false

Reproduce the installation using the supplied package.json with npm 10.5.0, Node.js 20.11.0, and the listed dependencies. Inspect node_modules/@typescript-eslint/utils/package.json and node_modules/typescript-eslint/node_modules/@typescript-eslint/utils to verify whether version 7 is resolved and nested as described; done means npm consistently installs the expected versions.