[BUG] Supabase installs into the user profile when installing as administrator #5604

Describe your issue

When installing the Supabase CLI through UniGetUI with the "Install as administrator" option, the executable is still installed under the current user's home directory:

C:\Users\me\node_modules\@supabase\cli-windows-x64\bin\supabase.exe

I expected the elevated installation to use:

C:\Windows\System32\node_modules\@supabase\cli-windows-x64\bin\supabase.exe

The user-profile location is used repeatedly, even when installing as administrator. Please clarify whether this is intended behavior or whether the npm installation scope / working directory is being handled incorrectly. The System32 path above is my expected location, rather than a verified requirement of npm or Supabase.

Steps to reproduce the issue

1. Find the Supabase CLI package in UniGetUI (npm).
2. Install it using the "Install as administrator" option and approve elevation if prompted.
3. Check the location of the installed executable.
4. Observe that it is under C:\Users\me\node_modules\@supabase\cli-windows-x64\bin\supabase.exe.

UniGetUI Version

Not yet available.

Windows version, edition, and architecture

Windows Pro, version 26H2, build 26300.9711, x64.

UniGetUI Log

Not available in this initial report.

Package Managers Logs

Not available in this initial report. The exact command generated by UniGetUI has not been captured, so use of --global or a custom prefix has not been verified.

Relevant information

Node.js 24.22.1 is installed system-wide at C:\Program Files\nodejs\node.exe. A check in the user's home directory found supabase@2.122.0 as a local npm dependency. Running npm config get prefix in a normal, non-elevated shell returned %APPDATA%\npm.

Latest-release reproduction and the FAQ checklist have not yet been confirmed. No claim is made that the underlying cause has been identified.