In Node.js 17.0.0, the V8 JavaScript engine has been updated to V8 9.5. Node.js 17 also comes with a command-line option, -no-extra-info-on-fatal-exception, to omit this extra information. It’s useful to provide this by default as often when diagnosing reported errors one of the first questions asked will be ‘What Node.js version are you using?’. In Node.js 17, the Node.js version will be included at the end of the stack trace when there is a fatal exception that causes the process to exit. Stack traces are an essential part of diagnosing application errors, helping to provide visibility into what has gone wrong. The following simple example illustrates the basic use of the readline module: import * as readline from ‘node:readline/promises’ import įor more details on the OpenSSL 3.0 release please see the OpenSSL 3.0 release post. The readline module provides an interface for reading data from a Readable stream (such as process.stdin) one line at a time. In Node.js 17, we introduce promise-based APIs for the Readline module. In recent years, we have added the Timers Promises API and Streams Promises API (both available since Node.js 15). Additional Promisified APIsĪ continuing strategic initiative within the Node.js project is to provide promise-based Node.js core APIs. We care about minimizing the number and disruption of these breaking changes for the stability of the platform and to make version migrations easier for our users. This means that the majority of new commits that are included in the initial major release (v17.0.0) are those that involve breaking changes. Some of the new changes and features delivered in Node.js 17 include:įollowing our Release Policy, new features that are contributed to the runtime are shipped approximately every two weeks in our ‘current’ release line. Similarly, you can find the release post at, which contains the list of commits included in this release. You can read more about our release policy at. As an odd-numbered release line, Node.js 17 will not be promoted to LTS. You can expect new releases of Node.js 17 approximately every two weeks, keeping you up to date with the latest features and changes. Node.js 17 replaces Node.js 16 as our ‘current’ release line, with Node.js 16 being promoted to long-term support (LTS) next week.
We’re excited to announce that Node.js 17 was released today! This blog was written by Bethany Griggs, with additional contributions from the Node.js Technical Steering Committee and project collaborators.