Submit command may not be respecting the HTTP_PROXY setting.

[xxnuo]

Describe the bug

Due to poor network conditions, I need to use a proxy to access Google.
However, during the refresh token process, I noticed that WXT does not adhere to the system's proxy-related settings including HTTP HTTPS ALL_PROXY.
Therefore, I am unable to use the submit command properly.

Reproduction

On this opensource project

https://github.com/xxnuo/jizhi-mod/

Steps to reproduce

echo $HTTP_PROXY
http://127.0.0.1:7890

pnpm wxt submit init
ℹ Initialize or update an existing .env.submit file.                                                                           1:39:15 PM

...

✔ Generate new refresh token?
Yes
[1:39:24 PM] https://accounts.google.com/o/oauth2/auth?response_type=code&scope=xxxx

✔ Open the above URL, login, and enter the auth code:
xxx

 ERROR  [POST] "https://accounts.google.com/o/oauth2/token": <no response> fetch failed                                         1:40:04 PM

  at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
  at async $fetch2 (node_modules/.pnpm/[email protected]/node_modules/ofetch/dist/shared/ofetch.897a6909.cjs:274:15)
  at async initChrome (node_modules/.pnpm/[email protected]/node_modules/publish-browser-extension/dist/cli.cjs:3614:17)
  at async init (node_modules/.pnpm/[email protected]/node_modules/publish-browser-extension/dist/cli.cjs:3535:26)
  at async CAC.<anonymous> (node_modules/.pnpm/[email protected]/node_modules/publish-browser-extension/dist/cli.cjs:3907:5)

System Info

System:
    OS: macOS 14.5
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12600KF
    Memory: 34.56 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.8.0 - /usr/local/bin/node
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 9.10.0 - ~/Library/pnpm/pnpm
    bun: 1.1.27 - /usr/local/bin/bun
  Browsers:
    Chrome: 128.0.6613.138
    Safari: 17.5
  npmPackages:
    wxt: ^0.19.7 => 0.19.7

Used Package Manager

pnpm

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[aklinker1]

I know nothing about http proxies, how to set one up, or how to use them :/

If you're willing to contribute, the code is available at: https://github.com/aklinker1/publish-browser-extension

[xxnuo]

Alright, I'll give it a shot😂