[BUG] npm install a specific package version in workspaces do not work as expected

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

I have two workspaces workspace_a and workspace_b using the same package dependency_a with different versions.

Changing the version of dependency_a in workspace_a using npm i dependency_a@version -w workspace_a have no effect and the version is not changed

Expected Behavior

Running npm i dependency_a@version -w workspace_a should change the version of dependency_a in workspace_a to the request version.

Steps To Reproduce

// Initialize project
$ npm init

// Initialize workspaces
$ npm init -w ./packages/a -w ./packages/b

// Install react 17 in all workspaces
npm install react@17.0.2 --workpaces

// Install react 18 in workspace a
npm install react@18.2.0 --workspace a

// Install back react 17 in workspace a
npm install react@17.0.2 --workspace a

The last command to install react with version 17 to workspace a have no effect, and workspace a still use react 18 at this point. The output of the last command is:

up to date, audited 10 packages in 709ms

found 0 vulnerabilities

Environment

• npm: 9.5.1
• Node.js: v18.16.0
• OS Name: MacOS 12.5
• System Model Name: Macbook Pro

Start by reproducing the issue with the listed npm init and workspace commands on npm 9.5.1 and Node.js v18.16.0. Compare workspace a after installing react@18.2.0 and then react@17.0.2; done means the final command changes workspace a to the requested version.