68112bada4
* chore(release): 11.28.5, pacquet 12.10.0 * docs(release): curate the 11.28.5 and 12.10.0 release notes Add a lead paragraph to each page and group the patch entries under subject headings, with the security fixes first. - Merge the unpublish path-boundary fix into the unpublish entry, the legacy metadata cache prune into the metadata cache entry, the two binary size entries, and the two 64 MiB archive limits on the v11 page. - Drop the manifest-utils saveType entry from the CLI page: the CLI only passes saveType values derived from its own flags, so no CLI user can reach the fixed path. - Rewrite mechanism-only entries (PAX header validation, bundled dependency symlinks, custom resolutions under name@version keys, proxy setting validation) in terms of what the user sees. - Use one link style for pnpm/pnpm issues. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@pnpm/network.proxy-agent
Creates an http/s/socks proxy agent
Create a http/s/socks proxy agent from uri and options.
This is usually used from within the agent component, to create an agent or proxy agent according to the config.
The return agent will match the proxy protocol (http / https / socks).
API:
function getProxyAgent(uri: string, opts: AgentOptions)
Available configuration (AgentOptions):
/**
* A proxy server for out going network requests by the package manager
* Used for both http and https requests (unless the httpsProxy is defined)
*/
httpProxy?: string;
/**
* A proxy server for outgoing https requests by the package manager (fallback to proxy server if not defined)
* Use this in case you want different proxy for http and https requests.
*/
httpsProxy?: string;
/**
* A path to a file containing one or multiple Certificate Authority signing certificates.
* allows for multiple CA's, as well as for the CA information to be stored in a file on disk.
*/
ca?: string;
/**
* Whether or not to do SSL key validation when making requests to the registry via https
*/
strictSsl?: string;
/**
* A client certificate to pass when accessing the registry. Values should be in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines replaced by the string "\n". For example:
* cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
* It is not the path to a certificate file (and there is no "certfile" option).
*/
cert?: string;
/**
* A client key to pass when accessing the registry. Values should be in PEM format with newlines replaced by the string "\n". For example:
* key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----"
* It is not the path to a key file (and there is no "keyfile" option).
*/
key?: string;
License
MIT