[BUG] `npm i` creates wrong symlinks inside workspaces

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

When workspace packages/bar has workspace packages/foo as a dependency npm i creates invalid foo symlink inside packages/bar/node_modules folder.

Folder structure and packages/bar/package.json file:

readlink packages/bar/node_modules/foo prints ../packages/foo.

Expected Behavior

npm i creates valid symlinks inside workspace node_modules folder.

readlink packages/bar/node_modules/foo prints ../../../packages/foo.

Steps To Reproduce

Repro is here https://github.com/iyegoroff/npm-workspaces-symlink-bug

npm i
npm start -w packages/bar

The output will be an error: sh: ./node_modules/foo/index.js: No such file or directory.
Correct output should be foo works!.

This also reproduces when running Github Actions.

Environment

• npm: 8.10.0
• Node.js: 17.9.0
• OS Name: macOS 12.3.1
• System Model Name: Mac mini

Start with the linked reproduction repository and run npm i followed by npm start -w packages/bar; inspect the packages/bar/node_modules/foo symlink with readlink. Trace the npm workspace installation path that creates this link. Done means the link resolves to ../../../packages/foo and the command prints foo works!.