@npmcli/agent
5.0.2 · 19 Jun 2026ISC25.6M / weekRepositoryHomepagenpmAtom feed
Upgrading @npmcli/agent From 1.1.0 to 5.0.2
12 releases in betweenevery note read
Reading releases, release notes and advisories…
- 4
- changes to make
- 0
- advisories fixed
- 3
- new
- 11
- fixes
Before you upgrade
Tick each one off as you go- Breaking5.0.0
- Breaking4.0.0
- Breaking3.0.0
- Breaking2.0.0
Release by release
- Fixed
Retain idle timeout for free sockets
- Fixed
- Fixed
Don't put opts.headers into the agent itself
- Fixed
Dispatch pending requests when a connection fails
- Fixed
- Breaking
@npmcli/agentnow supports node^22.22.2 || ^24.15.0 || >=26.0.0 - New
Bump to new node engine range
- Breaking
- Fixed
Use node 24 in ci
- Fixed
- Breaking
@npmcli/agentnow supports node^20.17.0 || >=22.9.0 - Fixed
Align to npm 11 node engine range
- Breaking
- Breaking
@npmcli/agentnow supports node^18.17.0 || >=20.5.0 - Fixed
Align to npm 10 node engine range
- Breaking
- Fixed
Set socks proxy socket family
- Fixed
- Fixed
Properly differentiate http and https proxies
- Fixed
21 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.