Debugging Node.js Upgrades

on YouTube ↗26m

" summary

Upgrading from Node 14 to 16 breaks a client because a commit (net auto destroy socket) changes socket/stream behavior: Node 14 emits an error when writing to a destroyed socket but Node 16 does not, so tests hang waiting for an event that never fires. Debugging path: isolate failing test, run Chrome inspector, use git bisect to find the commit, enable NODE_DEBUG to inspect runtime logs, then confirm with a minimal Node core reproduce and patch the client to emit the missing callback. Continuous CI on odd releases catches this earlier.

AI-written summary · about

" chapters (8)

1. 0:00Node.js upgrades intro
2. 3:50Upgrading Node.js challenges
3. 6:16Node.js releases and versioning
4. 10:11Debugging failing tests
5. 13:20Git bisect for breaking changes
6. 17:42Minimal Node.js core reproduce
7. 20:37Debugging techniques summary
8. 22:02Preparing for Node.js upgrade

" related talks

• 23mDebugging Your Way Through a Node.js UpgradeBethany Griggs · OpenJS World 2022
• 22mThe Journey About How I Fixed a Bug in the Node.js Core That Affected Thousands of PackagesErick Wendel · JSConf Korea 2022
• 23mThe Journey About How I Fixed a Bug in the Node.js Core that Affected Thousands of P...Erick Wendel · OpenJS World 2022
• 39mNode.js - What's Next - Catalyzing Change in the Node.js EcosystemMichael Dawson, Jean Burellier · OpenJS World @ Open Source Summit Europe 2023
• 30mNode.js Deep DebuggingGireesh Punathil · OpenJS World 2021
• 39mNode.js - What's Next - Catalyzing Change in the Node.js EcosystemMichael Dawson, Jean Burellier · Open Source Summit Europe 2023
• 26mHow Fixing a Bug in NodeJS Accidentally Doubled PerformanceTymur Shemsedynov · OdessaJS 2015
• 29mNode.js: The New and the ExperimentalBethany Griggs · OpenJS World 2021