feat: modernize deps, replace spdy with node:http2, migrate CI to GitHub Actions

[FacePlant101]

Summary

The spdy package hard-crashes on Node 22+ (process.binding('http_parser') removed), making the CLI completely broken on modern Node. This PR replaces it with the built-in node:http2 module, modernizes all dependencies to their latest CJS-compatible versions, and removes the stale @juji/cookie-manager dependency entirely.

Key changes

lib/trace.js rewrite — spdy → node:http2:

The old code used spdy.createAgent() for all HTTPS requests. Now HTTPS and HTTP use separate code paths:

_follow(url, ms)
  ├── https: → _followH2(parsed, ms)   // node:http2 session + stream
  └── http:  → _followH1(parsed, ms)   // node:http (unchanged behavior)

_followH2 opens an http2.connect(origin) session, sends HEAD via session.request(), and maps the HTTP/2 response:

• statusCode ← :status pseudo-header
• statusMessage ← '' (HTTP/2 has no reason phrase)
• httpVersionMajor/Minor ← 2/0
• headers ← response headers with pseudo-headers stripped

Trace.setProtocol() removed — protocol is known statically per code path.

Other code changes:

• url.parse() → new URL() (avoids DEP0169 deprecation)
• util.inherits() → class Trace extends Stream.Readable
• @juji/cookie-manager removed — replaced with an inline Cookies class (~35 lines) covering store(), prepare(), and length
• normalizeUrl() call gains sortQueryParameters: false (v5 sorts by default, v1 did not)
• Fixed _setCookie bug: was always storing headers['set-cookie'][0] in the loop instead of [i]
• Fixed redirect handling: resolve relative Location headers against current URL using new URL(location, currentUrl).href

Dependency bumps:

Package	Before	After
spdy	^3.4.4	removed
cookie-manager / @juji/cookie-manager	^0.0.19	removed (inlined)
chalk	^2.3.0	^4.1.2
normalize-url	^1.9.0	^5.3.1
readable-stream	^2.3.3	^4.7.0
standard	^9.0.2	^17.1.2
tape	^4.8.0	^5.10.2

Tests: Replaced broken test URLs (NYT returns 403, Twitter was already skipped) with google.com which reliably returns 200. All tests pass with 0 skips.

CI: Travis CI (.travis.yml) → GitHub Actions (Node 22, 24, 26 matrix).

engines: Added "node": ">=22".

All standard v17 lint warnings fixed (var → const/let, object shorthand).

Link to Devin session: https://app.devin.ai/sessions/31e62f90db4c4e19a7a1eed5302f18e8
Requested by: @avassdal

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​chalk@​4.1.2
	npm/​readable-stream@​4.7.0
	npm/​normalize-url@​5.3.1
	npm/​standard@​17.1.2
	npm/​tape@​5.10.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/tape@5.10.2 → npm/standard@17.1.2 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm eslint-plugin-react is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/standard@17.1.2 → npm/eslint-plugin-react@7.37.5 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eslint-plugin-react@7.37.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/standard@17.1.2 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report