Configure Bower’s Project Proxy in .bowerrc

For a checkout that still uses Bower, a project-local .bowerrc can supply the route for package HTTP requests:

{
  "directory": "bower_components",
  "proxy": "http://proxy.example.net:8080",
  "https-proxy": "http://proxy.example.net:8080"
}

Merge the proxy fields into the existing JSON object. Preserve the project's actual directory setting if it differs from the example. A shell assignment such as SET HTTP_PROXY=... is not a JSON entry.

proxy applies to HTTP destinations; https-proxy applies to HTTPS destinations. Both can name the same HTTP proxy endpoint. For public package downloads on a route allowing unauthenticated public intermediaries, the HTTP proxy list offers candidates for those values. The proxy's own transport scheme is part of the value.

Bower combines configuration from command-line arguments, environment variables and configuration files. A project file is therefore one input, not proof of the final effective value. The documented environment form includes names such as bower_https_proxy.

Keep the working directory consistent in automation. Bower searches the working-directory hierarchy for configuration, so starting the job in a different directory can change which project file participates. If retrieval delegates to Git, inspect the separate Git checkout route.