Custom registry ignored when downloading pnpm during vp-setup #1794

Describe the bug

When specifying a custom npm registry via the interactive customize menu in vp-setup, pnpm is still downloaded from https://registry.npmjs.org/ instead of the configured registry URL.
I ran into this while installing vp with vp-setup.exe on Windows 10 in an air-gapped environment.

Reproduction

/

Steps to reproduce

No response

System Info

windows 10

Used Package Manager

npm

Logs

upgrade.log

=== stdout ===

=== stderr ===
�[1m�[31merror:�[39m�[0m error sending request for url (https://registry.npmjs.org/pnpm/-/pnpm-10.33.0.tgz): client error (Connect): 远程主机强迫关闭了一个现有的连接。 (os error 10054)

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.