Are you a Node.js user? We want your feedback. Tell us all about how you're using Node.js in our annual user survey. Your response helps shape our future priorities! linuxfoundation.surveymonkey…

Node.js Interactive 2026 brought together the developers and maintainers shaping the future of Node.js. ⚡️ The event covered practical work happening across the project, including built in TypeScript support, node:test, QUIC and HTTP/3, documentation tooling, integration testing, and AI assisted development. The conversations also highlighted an important part of building Node.js: strong testing, security, documentation, and maintainer support remain essential as the ecosystem evolves. Read the full Node.js Interactive 2026 recap 👇 bit.ly/4gix0zB Huge thanks to @aviv_keller for the recap.

The Node.js Interactive speaker lineup at RenderATL is here. This is the program we've been building — technical talks from the people actively working on Node.js core, its ecosystem, and the tools developers ship with every day. What's on the schedule: → QUIC and HTTP/3 landing in Node.js core → Built-in TypeScript, node:test, node:sqlite, and the Permission System in Node 26 → Event loop diagnostics under real production load → MCP and spec-driven development for Node.js backends → The npm supply chain economy after Shai-Hulud and Axios → doc-kit replacing 14 years of documentation infrastructure → Integration testing patterns for complex Node.js systems → Platform engineering fundamentals for the AI era → SemVer build metadata as an extension point for package management → JavaScript governance, WinterCG, and cross-runtime interoperability → Open sourcing production systems sustainably Every talk connects back to what Node.js developers are building, maintaining, and protecting right now. Full speaker list: openjsf.org/blog/node-intera… Join us in Atlanta: renderatl.com/node

Guess who's back? 👀 Node.js Interactive returns at RenderATL 2026. Join maintainers, contributors, and developers for two days of talks on Node.js performance, security, AI tooling, infrastructure, and the real world challenges of running JavaScript at scale. See you in Atlanta. Details: openjsf.org/blog/nodejs-inte…

⚠️ Node.js 20 is officially End-of-Life. Staying on an unsupported version introduces significant security risks, but we know migration takes time. Join members of the Node.js Technical Steering Committee Matteo Collina and Marco Ippolito as we discuss how to navigate this transition safely. We’ll cover: ✅ The logic behind the new release cadence leading to Node 27. ✅ How the project is defending against the surge of AI-generated CVE reports. ✅ Support options for those unable to migrate off Node 20 immediately. Don’t leave your production environment to chance. Hear directly from the maintainers. 📅 May 27 | 11:00 AM EST 👉 Register for the live session: bit.ly/4tzcAqE

ICYMI (and we hope you didn't): Node.js 20 went EOL last week. But you have options. Check out our EOL support: nodejs.org/en/about/eol

With a security release deadline to meet, we interleaved the hash exploration, statistical evaluation, V8 implementation, and performance testing during the development. More details in the blog post.

We identified the vulnerable code paths across V8, refactored to improve efficiency in seed accesses, and implemented the new hash both in runtime C++ and the JIT compiler. Preliminary testing in the classic JavaScript benchmarks showed no noticeable regressions.

To address this, we designed a hash that alternates between xorshift and multiply with randomly generated multipliers. This descends from a family of mixers widely used in the industry. You can find cousins of it in Java's SplittableRandom, MurmurHash3's finalizer, and many others.