Node.js opens a new window has always been an essential part of the tech stack for many companies and developers. And here at OmbuLabs opens a new window and UpgradeJS opens a new window we use it too, due to its efficiency, scalability, and the robust ecosystem it provides.

Recently, the Node.js team released version 20 opens a new window , bringing with it a host of new features and improvements. In this post, we’ll highlight some notable changes opens a new window and explain why and how to upgrade to Node.js 20.x.

• Why upgrade?
  • Permission Model
  • V8 11.3
  • Stable test runner
  • Performance
  • Single Executable Apps (SEA)
  • Web Crypto API
  • Official support for ARM64 Windows
• How to upgrade
• Changes to address
  • Assert module
  • Asynchronous context tracking
  • Buffer
  • Command-line API
  • Crypto
  • ECMAScript modules
  • File system
  • Global objects
  • HTTP
  • HTTP/2
  • HTTPS
  • Net
  • Path
  • Performance measurement APIs
  • Process
  • Stream
  • Test runner
  • TLS
  • URL
  • Util
  • V8
  • WebAssembly System Interface (WASI)
  • Web Crypto API
  • Worker threads
• Conclusion

Why upgrade?

The latest version introduces several new features and enhancements opens a new window that make Node.js more secure, efficient, and improve the overall development experience. Below is the list of the notable introduced features.

Permission model

The Node.js Permission Model is an experimental feature that provides developers with more control over file system access by allowing them to restrict access to specific resources. This enables more secure and granular control over access to resources such as the file system, child processes, worker threads, and native addons.

V8 11.3

The update to V8 engine version 11.3 brings performance improvements and new language features. Also included are new methods on Array.prototype and TypedArray.prototype to enable changes on the array by returning a new copy of it with the change, and more.

Stable test runner

The test_runner module in Node.js version 20 has been marked as stable, providing a solid foundation for authoring and running tests.

Performance

Node.js 20 includes performance improvements to fundamental runtime elements like URL, fetch(), and EventTarget. These improvements can lead to a better user experience and lower resource usage. The Performance team is also actively seeking contributors, offering opportunities for developers to directly influence and improve Node.js’ performance.

Single Executable Apps (SEA)

Support for Single Executable Applications (SEA) has been added to Node.js. This feature, still experimental, allows for the creation of standalone applications, which can simplify distribution and execution, potentially expanding the use cases for Node.js applications.

Web Crypto API

Node.js 20 improves interoperability with other JavaScript environments by aligning the coercion and validation of Web Crypto API functions’ arguments with their WebIDL definitions. This can facilitate the integration of Node.js applications with other systems and standards, potentially leading to more flexible and versatile applications.

Official support for ARM64 Windows

Node.js now officially supports ARM64 Windows, providing native execution on this platform. This can extend the reach of Node.js applications by allowing them to run on a wider range of platforms and architectures.

How to upgrade

The upgrade of the Node.js version is different for every application, the process can’t look like a one-size-fits-all solution. However, there are some general steps that you can follow to make the upgrade process as smooth as possible. In our The Basics Of The Node.js Version Upgrade Process opens a new window blog post we have explained the general steps that you can follow to upgrade your Node.js version. We recommend that you read it before you start the upgrade process.

To make the process less complicated we have collected all the changes that were made after the release of Node.js 18.16.1. Read the next section - Changes to address - to learn more about them. With this knowledge in hand, you will be able to upgrade your Node.js version with more confidence.

Changes to address

Assert Module

• assert.CallTracker: The assert.CallTracker opens a new window class has been deprecated opens a new window and will be removed in a future version, consider using mock instead.

Asynchronous context tracking

• AsyncResource.bind(): The asyncResource property added to the returned bound function has been deprecated opens a new window and will be removed in a future version with no replacement.

Buffer

• Buffer.alloc(), Buffer.allocUnsafe(), Buffer.allocUnsafeSlow(): Now throws opens a new window ERR_OUT_OF_RANGE instead of ERR_INVALID_ARG_VALUE for invalid input arguments.

Command-line API

• --no-network-family-autoselection: The flag was renamed opens a new window from --no-enable-network-family-autoselection (added in v19.4.0) to --no-network-family-autoselection. The old name can still work as an alias.
• --experimental-global-customevent and --experimental-global-webcrypto: These options were removed opens a new window and the classes are now available by default, to disable them use --no-experimental-global-customevent and --no-experimental-global-webcrypto.
• --experimental-specifier-resolution: Flag was removed opens a new window .
• --experimental-test-coverage: Now can be used opens a new window with --test.
• --experimental-wasi-unstable-preview1: This option is no longer opens a new window required as WASI is enabled by default, but can still be passed.
• --test. --test-name-pattern, --test-reporter, --test-reporter-destination, --test-only, : The test runner is now opens a new window stable.

Crypto

• crypto.DEFAULT_ENCODING: property was removed opens a new window with no replacement.
• 'hash' and 'mgf1Hash' rsa-pss keygen parameters: Were replaced with hashAlgorithm and mgf1HashAlgorithm, and old parameters are deprecated opens a new window in runtime.

ECMAScript modules

• import.meta.resolve(): Now returns opens a new window a string synchronously instead of a Promise.
• resolve(): Now returns opens a new window object or promise, additionally the returned object has a new property - importAssertions.

File system

• filehandle.readableWebStream(): Added opens a new window option to create a ‘bytes’ stream.
• fsPromises.cp(), fs.cpSync(), and fs.cp(): Now accept opens a new window an additional mode option.
• fsPromises.opendir(),fsPromises.readdir(), fs.opendirSync(), fs.readdirSync(), fs.readdir(), and fs.opendir(): Added opens a new window recursive option.
• fsPromises.symlink(): If the type argument is null or omitted, Node.js will autodetect opens a new window target type and automatically select dir or file.
• fs.watch(): Added opens a new window recursive support for Linux, AIX and IBMi.
• fs.write(), fs.writeFileSync(), and fs.writeFile(): Passing to the string parameter an object with an own toString function is no longer supported opens a new window .

Global objects

• Crypto, crypto, CryptoKey, SubtleCrypto: No longer opens a new window behind --experimental-global-webcrypto CLI flag, enabled by default.
• CustomEvent: No longer opens a new window behind --experimental-global-customevent CLI flag, enabled by default.

HTTP

• http.createServer(): The highWaterMark option is supported now opens a new window .
• http.globalAgent: The agent now uses opens a new window HTTP Keep-Alive by default.

HTTP/2

• event: 'unknownProtocol': This event will only be emitted opens a new window if the client did not transmit an ALPN extension during the TLS handshake.

HTTPS

• https.globalAgent: The agent now uses opens a new window HTTP Keep-Alive by default.

Net

• socket.connect(): The default value for the autoSelectFamily option is now opens a new window true, also the default value for autoSelectFamily option can be changed at runtime using setDefaultAutoSelectFamily or via the command line option --network-family-autoselection.
• net.createServer(): The highWaterMark option is supported now opens a new window .

Path

• path.format(): The dot will be added opens a new window if it is not specified in ext.

Performance measurement APIs

• A lot of performance*.*() methods now must be called opens a new window with the proper object as the receiver.
• performance.mark(): The name argument is no longer opens a new window optional.

Process

• process.config: The object is now opens a new window frozen.
• process.exit() and process.exitCode: Coercion to integer was removed, now it only accepts opens a new window a code of type number, or of type string if it represents an integer.

Stream

• stream.finished(): Added opens a new window support for ReadableStream and WritableStream.
• stream.Duplex.from(): The src argument can now be opens a new window a ReadableStream or WritableStream.

Test runner

• The test runner is now opens a new window stable.
• Reporters are now opens a new window exposed at node:test/reporters.
• run(): Added opens a new window a testNamePatterns option.

TLS

• tls.createServer(): If ALPNProtocols is set opens a new window , incoming connections that send an ALPN extension with no supported protocols are terminated with a fatal no_application_protocol alert.

URL

• new URL(), url.domainToASCII(), url.domainToUnicode(): ICU requirement is removed opens a new window .
• url.parse(): Added support opens a new window for --pending-deprecation, also use of invalid ports in now deprecated opens a new window in runtime.
• url.urlToHttpOptions(): The returned object will also contain opens a new window all the own enumerable properties of the url argument.

Util

• util.parseArgs(): The API is no longer opens a new window experimental.

V8

• v8.getHeapSnapshot() and v8.writeHeapSnapshot(): Now support opens a new window options to configure the heap snapshot.

WebAssembly System Interface (WASI)

• new WASI(): Version field added opens a new window to options, the version option is now opens a new window required and has no default value, default value of returnOnExit changed opens a new window to true.

Web Crypto API

• No longer opens a new window experimental except for the Ed25519, Ed448, X25519, and X448 algorithms, WebCryptoAPI functions’ arguments are now opens a new window coerced and validated as per their WebIDL definitions like in other Web Crypto API implementations.

Worker threads

• worker.getHeapSnapshot(): Now supports opens a new window options to configure the heap snapshot.

Conclusion

Upgrading to Node.js 20 provides the chance to take advantage of numerous innovative features and improvements. However, like any significant upgrade, it requires thoughtful preparation, a tactical strategy, and appropriate tools.

Note that the cornerstone of a triumphant upgrade is in detailed readiness, rigorous testing, and a measured, systematic rollout.

If you’re seeking help upgrading to Node 18 or 20, we’re here to assist! We offer consulting services aimed at addressing technical debt and modernizing outdated Node.js applications opens a new window !