Packages

socks

2.8.11 · 19 Nov 2026MIT84.1M / weekRepositoryHomepagenpmAtom feed

Upgrading socks From 0.0.1 to 2.8.11

55 releases in betweennotes for 14

Reading releases, release notes and advisories…

2.0.0, 1.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below.
  1. 0.0.1yours
  2. 1.0.0major
  3. 6 releases
  4. 2.0.0major
  5. 46 releases
  6. 2.8.11target
?
changes to make
0
advisories fixed
?
new
?
fixes

Counted from 14 of 55 release notes. Advisories are counted from the advisory database, in full.

5 other lines we could not sort, mostly version bumps
  • Bump js-yaml and mocha

    2.8.10
  • Upgrade dev tooling and expand CI to current Node LTS versions

    2.8.10
  • When creating connections, 'ipaddress' can now be a hostname (proxyserver1.com for example)

    2.3.1
  • 'host' property added to proxy config, this is intended to replace 'ipaddress'. (ipaddress remains for backwards compatibility)

    2.3.1
  • Internally we now reference the socket as a duplex stream. Since (Socket instanceof Duplex === true) this shouldn't break anything, but you can now pass in a Duplex as existing_socket (if you're using this for some reason).

    2.2.0

1 internal line (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.