New Node.js Release

What is Node Js Used For?

It’s that season of the year again when the Node.js community publishes Node.js 18. This release will be upgraded to long-term support (LTS) in October 2022, implementing a well-defined procedure. Before that, we need the rest of the ecosystem to test it out and provide a review to the community. This will enable us to resolve any issues ahead of time and ensure that the version, ecosystem, and users are all prepared when it is released.

If you’ve been tracking the Node.js community activity or frequent updates, you’ll notice that the ecosystem goal is to concentrate their collective effort on features that are vital to consumers, such as:


● Releases that are consistent and predictable
● Support for the platform
● Safety
● Troubleshooting
● Efficiency
● Quality of the code and a safety net
● Characteristics

The Node.js 18 version comes with new features and developing work in the 18 time frame. The fascinating features are listed below.


● Test Runner
● ECMAScript modules improvements
● Experimental Fetch
● Updated Platform Support
● Improved support for AbortController and AbortSignal
● OPENSSL 3 Support
● V8 Version 10.1
● Default DNS resolution

As you can check from the above list, there’s a great deal of development going on, including groundbreaking new features like Test Runner support and Fetch, as well as continuous improvement on larger projects like ECMAScript module support. Add to that enhanced runtime environment, a new release of V8, and upgraded cryptography support, all of which are standard features of most versions, and it’s clear that Node.js is progressing nicely.

Node Js 18 Features

Experimental Test Runner

An experimental test runner is included in Node.js 18. It’s not meant to be a replacement for comprehensive tools like Mocha or Jest, but it provides a quick and simple way to execute a test suite without any further dependencies. It generates TAP output, which is extensively used and convenient to consume.

Experimental Fetch

An experimental prototype of the WHATWG Fetch was implemented shortly after the Next-10 mini-summit on Contemporary HTTP and Documentation. The conference concluded that a low-level and high-level API, with Fetch is the best option for the high-level API. It’s as easy as this to make a request:

const resp = await fetch(url)

mproving support for AbortController and AbortSignal

While AbortSignal and AbortController are not novel in Node.js 18, the Node.js codebase keeps growing in support. There were 11 SemVer minor PRs that added functionality related to AbortSignal, according to our estimate.

For example, you can now simply terminate an HTTP request while using fetch with the new updated AbortSignal.timeout().

const resp =

await fetch(‘http://slowsite.com’, {signal: AbortSignal.timeout(1000)});

ECMAScript Modules Improvements

Node.js has steadily improved after the release of ECMAScript module functionality. Since Node.js 17, the following features have been added:


● A command-line flag is no longer needed to use esm json modules (although it is still experimental).
● JSON Import Assertions in line with the TC39 proposal.
● Experimental support for HTTPS and HTTP impo1998e83983rts under the --experimental-network-imports flag.

In an attempt to optimize observability when using ECMAScript modules, work on broader efforts such as loaders and diagnostic channels is also ongoing.

Stream Improvement

There have been 6 SemVer minor and 11 SemVer minor modifications since the launch of Node.js 17. This adds the addition of several Experimental techniques to Readable streams, such as:


● toArray
● reduce
● filter
● forEach
● every
● some
● isReadable

V8 JavaScript Engine Version 10.1

This V8 JavaScript engine is the framework in which JavaScript code is executed. It’s what allows JavaScript to work on a variety of platforms, so programmers don’t have to worry about whether their code runs on Unix, Windows, or macintosh, or whether the OS’s hardware is x64, Arm, or PowerPC. Nevertheless, because V8 is built in C++, the Node ecosystem is responsible for maintaining and improving it for a variety of operating systems and hardware configurations.

Platform Support

This release upgrades the minimally supported versions for tooling and platforms needed to build Node.js, as it does with most utmost releases. These minimum acceptable levels are documented in Node’s development guidelines. The minimum glibc level necessary on Linux has been increased, which is noteworthy. This was essential since the Node.js program needs RHEL/Centos (now just RHEL) to create its release binaries, and RHEL/CENTOS 7 will be retired before the end of ecosystem support for Node.js 18.

OPENSSL 3 Support

Although Node.js 17 was the first big release to use OpenSSL 3 rather than OpenSSL 1.1.1, it’s worth reviewing because Node.js 18 will be the first big release promoted to LTS using OpenSSL3.

While the OpenSSL 3 APIs strive to be backward compatible with earlier OpenSSL versions, the migration to OpenSSL 3 will affect consumers because each new update of OpenSSL restricts the algorithms and key sizes that are accessible. If you’re still using small keys or outdated algorithms, set aside some time to figure out how you’ll be impacted.

Related Articles

Explore More Special Offers

  1. Short Message Service(SMS) & Mail Service

    50,000 email package starts as low as USD 1.99, 120 short messages start at only USD 1.00