Node.js 24: Everything You Need to Know in 2025

Quick Summary

Table of Contents

Introduction

The much-awaited Node.js 24 has been released on May 6th, 2025. The latest version offers several opportunities to provide new features and functionality that ease developers’ work.

Nevertheless, it is the current version, which will become the Long-Term Support (LTS) version in October 2025 and will be supported until April 2028. Until then, it will be the “Current” release for the next six months.

Node js 24 entices new advancements with the V8 engine update, which introduces features like Float16Array and RegExp.escape(). It also supports NPM 11, enhances developer experience with a global URLPattern, and has a smarter test runner.

This new release focuses on modern JavaScript, streamlined development, faster applications, and new upgraded functionalities. Here is the breakdown that highlights the latest advancements and their significant impact on productivity, performance, and security within the Node.js community.

What’s New in Node.js 24?: Latest Features and Functionalities

As we shift our attention to the newest capabilities and use cases of Node js 24, let’s find out what makes this release a significant step forward for the Node.js ecosystem. Here is a comprehensive overview of the latest features and functionalities introduced in Node.js 24.

1. V8 Engine Update: Modern JavaScript

The first update of what’s new in Node.js 24 is the upgrade to the V8 JavaScript engine, which is now at version 13.6 with modern JavaScript capabilities. This enhancement is designed especially to enhance performance, boost resource management, and provide developers with a powerful tool to develop dynamic applications:

• Float16Array
  The new typed array promotes the efficient representation and manipulation of half-precision floating-point numbers. It benefits performance-critical domains, such as graphics processing and certain numerical computations, where reduced memory footprint and potentially faster operations on lower-precision data are advantageous.
• Explicit Resource Management
  The new using and await using features provide structure and automatic cleanup tools for your code, such as network connections and files. It prevents problems and makes your code more reliable and easier to manage because it ensures these resources are properly disposed of when they are no longer needed.
• RegExp.escape()
  This static method helps you to escape special characters within regular expression strings. It provides a convenient way to perform on the RegExp constructor, eliminates manual escape needs, decreases error potential, and enhances regular expression security and clarity while handling user-provided or generated input.
• WebAssembly Memory64
  The enhancement indicates increased addressable memory space for WebAssembly modules within the Node.js environment. By supporting 64-bit memory, Node.js now offers computationally intensive execution and data-rich WebAssembly applications. It allows you to integrate high-performance codebases and originate from languages like Rust and C++.
• Error.isError()
  This utility function offers a more reliable and type-safe method to decide if a given value is an instance of the Error object. It enhances the robustness of application error handle logic by providing a clear and precise way to identify error objects, especially in complex scenarios that include cross-realm or custom error implementations.

2. AsyncLocalStorage defaults to AsyncContextFrame

Another latest advancement in Node.js 24 signifies a performance boost to the AsyncLocalStorage API by making AsyncContextFrame the default implementation for asynchronous context tracking.

However, under-the-hood optimization enhances the efficiency of multiplying contextual data, like request-specific information or transaction IDs, across asynchronous operations. Hence, the context is now streamlined and managed, and applications with complex asynchronous flows can experience lower overhead and better responsiveness.

In addition, the change is primarily for existing AsyncLocalStorage users. It offers performance benefits without the requirement of code modifications and a robust environment for advanced asynchronous patterns.

3. Test Runner: Enhancing Performance

With the enhanced built-in test runner in version 24, it now automatically waits for subsets. In simpler words, you do not need to manually await them. In previous versions, developers had to instruct explicitly, but with the new version of Node, it handles them innovatively and ensures all sub-tests finish their execution cycle before the runner proceeds.

Additionally, the manual overhead of managing sub-test completion is reduced, and Node.js 24 contributes to a more efficient and less error-prone testing workflow.

The Previous Approach (Pre-Node.js 24):
In earlier versions, it became difficult to manage subtests that demanded explicit use of await. Consider this structure:

The Streamlined Behavior in Node.js 24:
With Node.js 24, the test runner intelligently handles the execution flow of subtests. The need for manual await is now necessary:

4. NPM v11

Node.js 24 offers a significant update to npm, the tool you use to manage the libraries for your project needs. The new version, NPM 11, transforms execution and performance faster. Simply put, when you run command NPM, it will install everything (npm install).

Now, it will happen more quickly, which will help you save time and make your development process smoother. It also enhances ways to check code security issues and ensure the app remains safer.

Moreover, when you begin a new project (npm init), npm will now ask you what kind of project it is. Also, how it organizes the information in your project’s main settings file (package.json) is a bit different.

Some older features, like npm hook, have been removed. Also, it ignores scripts; as a result, overall changes have made npm a better experience.

5. Permission Model Enhancements

Introduced in Node.js 20, the experiment of the permission model has evolved in the updated version. It has become simpler, and instead of using –experimental-permission, you can now use a shorter and cleaner command: –permission.

The permission model improvement has become more stable and ready for wider use. Moreover, you can restrict your Node.js app and allow access like the network or the filesystem.

Note: In the recent Node.js v23 , this feature was considered ready for everyone to use reliably.

6. Removal of MSVC Support

Some older functions are no longer valid to run in your Node js project. A few of the previous tools and functions have either been removed or marked as deprecated, which means that they will eventually be removed in future versions.

It helps to keep your Node.js up-to-date with better and more standardized approaches. Here is the rundown of what’s being deprecated or removed:

• url.parse(): This old method of breaking down URLs is now outdated. It’s better to switch to the WHATWG URL API, which is cleaner, more consistent, and aligns with web standards.
• tls.createSecurePair(): This function has been completely removed. If your app uses it for secure connections, you’ll need to update it to use newer TLS APIs that are safer and better supported.
• SlowBuffer: This legacy approach to working with binary data is being deprecated. You should use the standard Buffer class instead because it is more efficient and better maintained.
• REPL without new: Performing a REPL session without the new keyword is now considered outdated. You should use the new REPL.REPLServer(…) to create a proper instance.
• Zlib classes without new: Similarly, if you are using compression streams like gzip or inflate, make sure you are instantiating them with new (e.g., new zlib.Gzip()).
• Passing args in spawn() and execFile(): The old way of passing arguments using the args option is being deprecated. It’s now recommended to pass your arguments directly in the command string or array for better clarity.
• Old-style fs constants (like fs.F_OK): These older file system flags are being replaced with updated constants that are more consistent across the platform.

7. Undici 7: Improved HTTP

The last on the list of what’s next in Node.js 24 is Undici 7.0.0, which is an updated version of modern HTTP client. It upgrades HTTP support and provides a smoother experience for those who use fetch() or build HTTP-heavy services. Utilizing Node js 24’s Undici, it makes web requests and receives responses quickly. As a result, it has rapid user loading times and efficient communications with external APIs.

Furthermore, Undici 7 enables your Node js apps to take advantage of new capabilities and communicate efficiently with modern web services. Also, an innovative HTTP client in Node.js enhances app performance and better compatibility with the wider web ecosystem.

What’s the First 5 Things to Do After Upgrading to Node.js 24?

To get the most out of the latest release, here are five smart steps you can take right after installing Node.js 24:

• Run node –version to confirm you are on v24 and your environment is set.
• Use tools like npx deprecate-check or linters to catch outdated patterns (url.parse(), SlowBuffer, etc.) and scan for deprecated APIs.
• Compare performance gains from the upgraded V8 engine through simple load testing and benchmark your app efficiently.
• Update third-party packages by operating npm outdated and update dependencies for Node 24 compatibility.
• Try a small project with Native ES Modules, test the improved ESM support for fresh script or service.

Conclusion