Ask the Maintainer: Nodejs
summary
Live Node.js clinic walks through concrete internals: the event loop runs on libuv thread pool with async APIs offloaded and callbacks queued in phased FIFO queues, timers can keep a process alive so timer keeps event loop alive, and heavy callback bursts run sequentially on one thread. Streams require backpressure handling using pause/drain/write patterns. For vulnerabilities the workflow uses CVE/HackerOne triage, no full automation yet—use npm audit, rely on actively maintained packages and raise issues on upstream repos.
AI-written summary · about
chapters (8)
- 0:00Introduction and event loop
- 8:40Handling Node.js vulnerabilities
- 14:24Event loop best practices
- 20:55Understanding events in Node.js
- 25:54Event loop behavior pitfalls
- 30:57Working with Node.js streams
- 36:58Server vs stream events
- 43:32Server-sent events vs long polling
related talks
21mThe Node.js Eventloop Fairytale
41mDissecting NodeJS - How it works under the hood
28mUnderstanding the NodeJS event loop myths and magic
49mA Journey into Node.js Internals
31mNodeJs Event Loop- 49mA Journey into Node.js Internals
22mScaling Node.js and unblocking the Event Loop
34mYou Don't Know Node.js