Systems | Development | Analytics | API | Testing

Libuv is one of the most crucial components behind Node.js, yet many developers aren't fully aware of its role in enabling asynchronous I/O operations. As a high-performance, cross-platform support library, Libuv is at the heart of event-driven programming in Node.js, but its impact extends far beyond that. Santiago Gimeno is a Libuv maintainer and Senior Software Architect at NodeSource.

With the release of Node.js v23.6.0, developers can now use TypeScript natively without additional transpilation tools like ts-node or manual compilation steps. This milestone significantly streamlines development workflows, simplifying build processes and improving the overall developer experience by reducing complexity.

Artificial intelligence is revolutionizing software development, and at NodeSource, we're bringing AI-driven insights to Node.js applications through N|Solid. Our latest AI-powered profiling and diagnostics tools help developers streamline performance analysis, optimize application efficiency, and proactively detect bottlenecks. In this post, we'll dive into how AI enhances observability, simplifies CPU profiling, and generates actionable recommendations that improve performance debugging workflows.

Tracing is a critical feature in N|Solid that allows developers to analyze application performance by visualizing the relationships between different processes through spans and traces. Without proper tracing, debugging performance issues becomes significantly more challenging, as developers lack visibility into how requests flow through an application. Tracing helps pinpoint bottlenecks, optimize request execution, and improve overall application efficiency.

When debugging performance issues in a Node.js application, CPU profiles play a crucial role in identifying bottlenecks. However, if your code is transpiled or minified, analyzing these profiles can be a challenge. This is where sourcemaps in N|Solid come in, helping you trace your code back to its original form for more meaningful insights.

Keeping your Node.js version up to date is essential for security, performance, and access to the latest features. New releases often include bug fixes, optimizations, and improvements that can enhance your development workflow. If you're using Windows, there are multiple ways to update Node.js, whether you prefer a simple installer, a package manager, or a version manager. In this guide, we’ll walk through different methods, so you can choose the one that best fits your needs.

Keeping your Node.js version up to date is essential for security, performance, and access to the latest features. New releases often include bug fixes, optimizations, and improvements that can enhance your development workflow. If you are running a Linux system, there are several ways to update Node.js. This guide will walk you through multiple methods, including using a package manager, Node Version Manager (nvm), NodeSource distribution binaries, and manually downloading the latest version.

Keeping your Node.js version up to date is essential for security, performance, and access to the latest features. New releases often include bug fixes, optimizations, and improvements that can enhance your development workflow. If you're using macOS, there are several ways to update Node.js. In this guide, we’ll walk through different methods, including Homebrew, Node Version Manager (nvm), and manual installation.

Node.js has revolutionized web development by enabling developers to use JavaScript, a traditionally client-side language, on the server side. Created in 2009 by Ryan Dahl, Node.js is an open-source, cross-platform runtime built on Chrome’s V8 JavaScript engine. This breakthrough has unified front-end and back-end development under a single language, transforming how modern applications are built.

The year is 2024 (yet), and Node.js has reached version 23, with two semver-majors released per year it might be difficult to keep track of all areas of Node.js. This article revisits the State of Node.js performance, with a focus on comparing versions 20 through 22. The goal is to provide a detailed analysis of how the platform has evolved over the past year. This is a second version of "The State of Node.js Performance" series.