Node.js - What's Next - Catalyzing Change in the Node.js Ecosystem
summary
Node 27 ships yesterday and Node 20 LTS goes live in about three weeks while Node 16 is EOL, so plan upgrades now. Core changes include the OpenSSL 3 upgrade that tightens supported algorithms (OpenSSL 3), DNS now respects server address order (IPv6-first can hang installs), a stable test runner in 20, a built-in argument parser, and a single executable bundling mode that runs only the bundled script (reducing surface area). WASI moves to explicit preview flags and a new diagnostic channel plus tracing aid observability.
AI-written summary · about
chapters (17)
- 0:00Node.js future changes
- 1:25Talk agenda
- 2:06Node.js ecosystem updates
- 5:37Recent Node.js features
- 10:52HTTP and Fetch API progress
- 12:38Developer experience improvements
- 15:42Single executable apps
- 17:05Process permissions model
- 18:11Diagnostics and tracing
- 19:34ARM64 expansion
- 20:15Next 10 project goals
- 23:47Community feedback priorities
- 25:13Mini-summits and deep dives
- 27:16Documentation initiatives
- 28:39New teams and groups
- 33:12Get involved in Node.js
- 35:18Q&A on single executable apps
related talks
39mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem
34mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem
29mNode.js: The New and the Experimental
25mNode.js - What's Next
22mWhat's New in Node.js Core?
27mNode.js 12: A Decade of Node.js
31mThe State of Node.js Core
24mNode.js 12: A decade of Node.js