Systems | Development | Analytics | API | Testing

At NodeSource, we are always striving to enhance the resilience, scalability, and openness of our tooling. Recently, we took a significant step forward by adopting gRPC in N|Solid —a widely used open-source protocol for efficient communication between systems. This move represents a major shift in how we transmit data internally while ensuring seamless continuity for our users.

At NodeSource, we pride ourselves on delivering the best tools and open source support for Node.js users. Staying aligned with the latest releases is a key part of that commitment. With the latest Long-Term Support (LTS) release, Node.js 22 (codenamed "Jod"), we continue to ensure our users have access to reliable, secure, and up-to-date **Node.js binaries **through our NodeSource Binary Distributions.

On October 29, 2024,* Node.js v22 officially transitioned into *Long Term Support (LTS) with the codename 'Jod'. For developers and organizations relying on the stability of Node.js for production environments, this transition marks a key milestone for Node.js 22.x, ensuring it will receive critical updates and security support for years to come. Let’s take a closer look at what this means, along with a refresher on the Node.js release lifecycle .

We're thrilled to announce the release of N|Solid 6, the latest version of our powerful tool designed to elevate your production Node.js applications and services. Packed with advanced features and enhancements, N|Solid 6 offers unparalleled insights and operational control, making it the go-to solution for monitoring, diagnosing, and securing your critical Node.js applications.

N|Solid Runtime, the OSS runtime that powers N|Solid Pro, is an innovative, lightweight runtime for Node.js applications. It offers real-time insights into performance, memory usage, and CPU consumption, giving developers unparalleled visibility into their code without requiring any modifications. In today’s software landscape, understanding your application's production behavior is crucial. With cloud-native architectures, microservices, and distributed systems, pinpointing issues is challenging.

We are thrilled to announce the release of a new feature in N|Solid that includes sample heap profiling and heap objects observability for main processes and worker threads. N|Solid is known for its Node.js performance and security observability and diagnostic tools and best-in-class low overhead has completed a new innovation to hunt memory leaks in development and production environments. Memory is a precious resource in computing.

Exciting news this week! One of the latest features in Node.js core is the addition of support for requiring synchronous ECMAScript Modules (ESM) graphs. This enhancement promises to simplify the transition for package authors and users alike, as the ecosystem gradually shifts towards ESM. This long-awaited feature, enabled via the --experimental-require-module flag, marks a pivotal moment in Node.js development, addressing a persistent pain point for developers.

At NodeSource, we understand the hesitance and scrutiny that often accompany claims of "Node.js compatibility". The Node.js ecosystem is vast and intricate, and as Matteo Collina rightly points out, passing a "hello world" example is just the start. We believe N|Solid should be a component of every Node.js project, especially in production, to provide developers and organizations with the most advanced performance and security observability tooling.

The year 2024 marks a crucial juncture in the Node.js ecosystem, where developers face different choices when it comes to selecting the right package manager for their projects. npm, Yarn, and pnpm stand out as the frontrunners, as they are the most widely used in the Node.js ecosystem. Each package offers unique features and capabilities tailored to address the challenges of modern development environments.

Two months into 2024, I’ve decided to summarize the achievements in the Node.js space from 2023. As always, this list is curated by me, so I may overlook some pull requests due to the vast amount of work completed by Node.js collaborators and areas where I need more context, such as WASI. Node.js is rapidly evolving, and it can be challenging for regular users to stay updated with the latest changes. Even as someone who works on the project, it’s possible to overlook certain commits.