Verify latest release

• I verified that the issue exists in the latest pnpm release

pnpm version

10.5.2

Which area(s) of pnpm are affected? (leave empty if unsure)

Store

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

# pnpm config list
cache-dir=~/.cache/pnpm
global-bin-dir=~/.local/share/pnpm
global-dir=~/.local/share/pnpm/global
registry=https://registry.npmmirror.com/
store-dir=~/.local/share/pnpm/store
user-agent=pnpm/9.15.3 npm/? node/v20.11.1 darwin x64

#  cat ~/.npmrc

registry=https://registry.npmmirror.com/

# pnpm
store-dir=~/.local/share/pnpm/store
global-dir=~/.local/share/pnpm/global
global-bin-dir=~/.local/share/pnpm
cache-dir=~/.cache/pnpm

Describe the Bug

When the pnpm install command is executed, a ~ directory will be created in the working directory. Sometimes the dependent packages are installed in the newly created ~ directory.

Expected Behavior

How to solve this problem?

Which Node.js version are you using?

v22.14.0

Which operating systems have you used?

• macOS
• Windows
• Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response