A recap of Node.js Interactive 2026, held inside RenderATL alongside Atlanta Tech Week, covering talks on maintainer sustainability, JavaScript governance (WinterTC/Ecma TC55), the npm supply-chain attacks of Shai-Hulud and the Axios compromise, a proposed SemVer build-metadata extension, platform engineering in the AI era, Node.js's growing built-in feature set, the shift to a single major release per year starting with Node.js 27, QUIC/HTTP-3 progress via node:quic, the new doc-kit documentation pipeline, integration testing tooling, and several talks on AI's role in Node.js development and performance.
Questions this post answers
When will Node.js move from two major releases a year to one?
Starting with the 27.x line, Node.js will switch from two major releases per year to one. An Alpha phase begins in October 2026, Node.js 27.0.0 becomes Current in April 2027, and it enters LTS in October 2027. Version numbers will align with the calendar year of their initial Current release, and every release will eventually become LTS. Teams planning Node.js upgrade cycles can track release schedule changes like this on daily.dev.
What was the Shai-Hulud npm supply chain attack and how many packages did it affect?
Shai-Hulud was a self-replicating attack that spread through compromised npm maintainer accounts starting in September, leading GitHub to remove more than 500 compromised packages. A second wave in November backdoored at least 796 packages representing more than 20 million weekly downloads, exfiltrating stolen credentials through public GitHub repositories. Developers securing their dependency chains follow npm supply-chain incidents like this on daily.dev.
How do I enable QUIC support in Node.js using node:quic?
Node.js's node:quic implementation is still experimental and requires a Node.js binary specifically built with experimental QUIC support, then started with the --experimental-quic runtime flag. The flag alone cannot add QUIC support to a binary compiled without it, since the feature must be compiled in first. Engineers evaluating HTTP/3 readiness in Node.js can follow QUIC implementation progress on daily.dev.
63.5K Impressions2 Comments