Deno’s Proxy Environment Covers Module Downloads Too

Set HTTP_PROXY and HTTPS_PROXY before launching Deno so its module downloads and fetch requests have the intended route.

Deno documents HTTP_PROXY and HTTPS_PROXY for both module downloads and fetch. Set them in the environment that launches the Deno process. For a POSIX shell:

export HTTP_PROXY='http://proxy.example:8080'
export HTTPS_PROXY='http://proxy.example:8080'
deno run --allow-net app.ts

The example uses an HTTP proxy listener for both destination schemes. Use the actual intermediary URL; the HTTP proxy list supplies candidates for permitted public module and API downloads. HTTPS_PROXY does not require the URL itself to start with https.

Launching with the variables already present covers downloads needed while loading the application. Code inside app.ts cannot configure the earlier network request required to obtain that code’s static imports.

Deno also documents NO_PROXY as a comma-separated list of hosts that bypass the proxy for module downloads and fetch. Keep its intended value in the same startup environment. Network permission and proxy routing remain separate inputs: choosing a proxy does not replace the application’s required permissions.

Artiglyn mynjee