Developers depend on Node.js every day. But most of them never see the work behind each release, security fix, and long-term decision that keeps it up and running, or how those decisions shape which versions teams can run, how they handle vulnerabilities, and even when they upgrade.
Node.js is changing its release schedule and AI is reshaping how vulnerabilities get reported, all while the demands on open source maintainers continue to grow, so there’s plenty to talk about during this session.
In this fireside chat, TuxCare’s Chris DeMars sits down with James Snell, a core contributor to Node.js and member of the Node.js Technical Steering Committee, for a candid conversation about what it really takes to maintain one of the most widely used JavaScript runtimes in the world, and where the project goes next.