NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #289 most downloaded on npm
Offers getProxyForUrl to get the proxy URL for a URL, respecting the *_PROXY (e.g. HTTP_PROXY) and NO_PROXY environment variables.
Last release 6 months ago
14 Mar 2026
Release timing varies
gaps range from 5 weeks to 5.9 years
Some releases are documented
notes for 3 of 7 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
7 releases · first in 2016
This version is identical to v2.0.0 , except it supports more old Node.js versions, as old as Node v10.0.0 ( #38 ).
This version is identical to v2.0.0, except it supports more old Node.js versions, as old as Node v10.0.0 (#38).
The most significant change between 1.x and 2.x is the transition from url.parse to the standard URL API. Check out the README to learn more about the difference.
Full Changelog: v2.0.0...v2.1.0
Remove url.parse usage to avoid DEP0169 DeprecationWarning ( #30 ).
Remove url.parse usage to avoid DEP0169 DeprecationWarning (#30).
Use WHATWG URL constructor to parse strings instead of url.parse.
This may cause getProxyForUrl to return an empty string instead of
a proxy URL when the input is an invalid URL.
Switch from CJS to ESM. When import syntax is used, the minimum
compatible Node.js version is v12.17.0. When require is used, the
minimum compatible Node.js version is v20.19.0, because that version
introduced require(esm) support.
Drop detection of npm_config_-prefixed environment variables, which
was introduced in 1.1.0. Now the behavior is back to version 1.0.0.
This should not affect users in practice, because the npn ecosystem
dropped support for these environment variables many years ago (#13).
Full Changelog: v1.1.0...v2.0.0
One column per quarter.
feat: fetch proxy configuration from NPM if any
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →