Systems | Development | Analytics | API | Testing

With the release of Node.js 24.11.0 “Krypton”, the Node.js 24 line has officially entered Long-Term Support (LTS) and will continue receiving maintenance and security updates through April 2028. This marks the beginning of a new stable era for production workloads, bringing developers enhanced security, stricter runtime behavior, and improved Web API support.

Express.js, one of the most widely used web frameworks in the Node.js ecosystem, is undergoing a major transformation. Once considered stable but stagnant, Express is now being revitalized with a clear governance model, a renewed focus on performance, and active collaboration from organizations like NodeSource.

JSConf North America 2025 brought together the brightest minds in the JavaScript ecosystem: from maintainers and contributors to companies driving innovation across runtimes, frameworks, and platforms. For NodeSource, this year’s event was especially meaningful, filled with major announcements, community recognition, and deep discussions about the future of JavaScript. Here are some of our biggest highlights from the week.

We’re excited to announce that NodeSource has joined the OpenJS Foundation’s Ecosystem Sustainability Program (ESP), a strategic partnership designed to sustain the health and reliability of the JavaScript ecosystem. Through the ESP, NodeSource will help provide security support for organizations running older, unsupported versions of Node.js, giving teams more time and flexibility to transition to newer releases while maintaining a secure posture.

Node.js 22 has entered into Long-Term Support (LTS) phase, a critical milestone that signals its stability and readiness for enterprise-level deployment. This release represents a significant push toward dependency elimination, core performance optimization, and enhanced developer experience.

Performance monitoring for Node.js has always been about two things: collecting the right telemetry and turning that telemetry into fast, confident action. With applications growing more distributed and expectations for reliability and speed rising, traditional dashboards and manual triage are no longer enough. For organizations running Node.js at scale, identifying performance bottlenecks, memory leaks, or CPU spikes can be complex and time-consuming.

Over the years, Node.js developers have relied on countless npm packages to fill gaps in the platform. From HTTP utilities to file system helpers, the ecosystem has always been one of Node’s greatest strengths. But as Node.js continues to evolve, many features that once required third-party packages are now built into the runtime itself. This shift reduces dependency bloat, improves security, and makes applications easier to maintain.