Skip to content

build: drop Node 18 EOL, add Node 24 and 25 support - #115

Closed
buffcode wants to merge 1 commit into
masterfrom
fix/handle-parser-errors
Closed

build: drop Node 18 EOL, add Node 24 and 25 support#115
buffcode wants to merge 1 commit into
masterfrom
fix/handle-parser-errors

Conversation

@buffcode

Copy link
Copy Markdown
Owner

Summary

  • Remove Node 18 from test matrix and engine requirements (Node 18 reached EOL in April 2024)
  • Add Node 24 and 25 to CI matrix and supported engines range
  • Update @types/node dev dependency range accordingly

Changes

  • .github/workflows/nodejs.yml: matrix ['18','20','22']['20','22','24','25']
  • package.json engines: ^18 || ^20 || ^22^20 || ^22 || ^24 || ^25
  • package.json @types/node: same range update

Wrap NtpPacketParser.parse() in try/catch inside the dgram message
listener so a parse failure rejects the pending promise cleanly
instead of escaping as an uncaughtException. This matters once the
parser lands input validation (it will throw TypeError on non-48-byte
or non-Buffer inputs); without this guard a single malformed UDP
response would crash the host Node process.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@buffcode buffcode self-assigned this Apr 21, 2026
@buffcode

Copy link
Copy Markdown
Owner Author

Closing this PR as it was accidentally opened from the wrong branch (fix/handle-parser-errors). The Node 18 EOL changes will be re-submitted from the correct branch build/node-18-eol.

@buffcode buffcode closed this Apr 21, 2026
@buffcode
buffcode deleted the fix/handle-parser-errors branch April 21, 2026 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant