[BUG] --force doesn't work as intended when automatically removing node_modules symlinks

[blaumeise20]

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 I have a symlink called node_modules to a different directory, then npm will remove this symlink and create a real folder. This has been introduced in npm/arborist@f2b0cee as a safety feature, but as it doesn't disable it as specified when using --force option.

Other people have similar problems too:

• [BUG] npm install deletes an existing symlinked node_modules directory #3669
• [BUG](arborist) should not remove global node_modules #4274

Expected Behavior

It should work as intended in npm/arborist@f2b0cee (don't remove symlink if --force).

I really needed this thing to work, so I had to downgrade npm to an older version.

Steps To Reproduce

1. Create an empty folder
2. Create a second folder inside the first one
3. Run npm init -y
4. Run ln -s your_folder_name node_modules
5. Run npm install --force <any package name>
6. node_modules no longer points to your_folder_name

Environment

• npm: v8.3.1
• Node.js: v17.4.0
• OS Name: MacOS Catalina
• System Model Name: iMac
• npm config:

; this only showed comments and registry auth token "(protected)"

[kaysond]

@blaumeise20 what version did you downgrade to?

[blaumeise20]

I am now using a pretty recent version from before adding this feature (restriction). I think it's v7.15, I don't have access to my home PC right now.