[BUG] Dependency hoisting in workspaces not working, depending on workspace name

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

If a workspace folder has the same name as one of its direct dependencies, that dependency will not be hoisted to the project root on install.

Note that behavior only applies for top-level dependencies. Nested dependencies will still be hoisted properly.

Expected Behavior

The dependency should be hoisted to the root.

I'm not entirely sure whether this is actually a bug or a constraint due to the Node module resolution algorithm or something similar. However, I have not found any official or inofficial documentation of this behavior. If the behavior is by design, this issue could at least serve as an anchor for other users who run into the same problem.

Steps To Reproduce

Follow the steps in the reproduction repository I made: loilo/repro-npm-workspaces-hoisting.

Environment

• npm: 8.5.3
• Node.js: 17.6.0
• OS Name: macOS 12.2.1
• System Model Name: MacBook Pro
• npm config:

; "builtin" config from /usr/local/lib/node_modules/npm/npmrc

prefix = "/usr/local" 

; "user" config from /Users/florian/.npmrc

//localhost:4873/:_authToken = (protected) 
//registry.npmjs.org/:_authToken = (protected) 
http://localhost:4873 = "" 

; node bin location = /usr/local/Cellar/node/17.6.0_1/bin/node
; cwd = /Volumes/RAMDisk/repro-npm-workspaces-hoisting
; HOME = /Users/florian
; Run `npm config ls -l` to show all defaults.

Start by running the steps in the loilo/repro-npm-workspaces-hoisting repository against the npm CLI and inspect the workspace dependency-hoisting behavior. Done means resolving the workspace-name collision while still hoisting the direct dependency to the project root, or documenting that the behavior is required by Node.js module resolution.