Node.js - What's Next - Catalyzing Change in the Node.js Ecosystem
summary
Node 20 ships features being backported into earlier LTS lines and becomes LTS in September while OpenSSL 3 forces many to skip 16; default DNS now prefers resolver order which may break misconfigured IPv6 setups and can be reverted with --dns-result-order. Core additions include fetch, the stable test runner, an argument parser, single executable applications using a postpack injector, process based permissions to limit file and spawn access, a tracing diagnostic channel, and a community survey that returned about 17,000 responses.
AI-written summary · about
chapters (19)
- 0:00Node.js future changes
- 1:03Tracking Node.js developments
- 3:53Node.js initiatives and meetings
- 5:19Node.js features and LTS updates
- 6:42OpenSSL 3 and DNS changes
- 9:13Experimental features in Node.js
- 12:23Node.js 20 features
- 15:13Node.js single executable apps
- 16:17Process-based permissions
- 17:20Diagnostics and tracing
- 18:43ARM and Windows on ARM
- 19:05Next 10 initiative priorities
- 23:18Next 10 summits feedback
- 26:33New teams and initiatives
- 27:17Teams driving Node.js
- 28:21Security team updates
- 29:46Performance team achievements
- 30:49WASI and UV WASI work
- 31:52Get involved in Node.js
related talks
39mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem- 39mNode.js - What's Next - Catalyzing Change in the Node.js Ecosystem
22mWhat's New in Node.js Core?
29mNode.js: The New and the Experimental
25mNode.js - What's Next
27mNode.js 12: A Decade of Node.js
24mNode.js 12: A decade of Node.js
31mThe State of Node.js Core