The Timers Promises API provides an alternative set of timer functions that return Promise objects, removing the need to use util.promisify(). > const matchObj = /(Java)(Script)/d.exec('JavaScript') undefined > matchObj.indices, ,, groups: undefined ] > matchObj.indices // Match > matchObj.indices // First capture group > matchObj.indices // Second capture group įor more information about the new features and updates in V8 check out the V8 blog. indices property on match objects when the regular expression has the /d flag. This update brings the ECMAScript RegExp Match Indices, which provide the start and end indices of the captured string. In Node.js v16.0.0, the V8 engine is updated to V8 9.0 - up from V8 8.6 in Node.js 15. V8 upgraded to V8 9.0Īs always a new version of the V8 JavaScript engine brings performance tweaks and improvements as well as keeping Node.js up to date with JavaScript language features. More details on our release plan/schedule can be found in the Node.js Release Working Group repository. Node.js 10 will go End-of-Life at the end of this month (April 2021). Once promoted to long-term support the release will be designated the codename ‘Gallium’.Īs a reminder - Node.js 12 will remain in long-term support until April 2022, and Node.js 14 will remain in long-term support until April 2023. As per the release schedule, Node.js 16 will be the ‘Current’ release for the next 6 months and then promoted to Long-term Support (LTS) in October 2021. Initially, Node.js 16 will replace Node.js 15 as our ‘Current’ release line. The Node.js blog post containing the changelog is available at. See PR #128123 for an example of how the Node.js version has been upgraded previously.You can download the latest release from, or use Node Version Manager on UNIX to install with nvm install 16. WORKSPACE.bazel - The version is specified in the node_version property.īesides this property, the list of files under node_repositories must be updated along with their respective SHA256 hashes.package.json - The version is specified in the engines.node field.If they are not, and the update is urgent, you can skip this file and update it later once Docker Hub has been updated. Note that Docker Hub can take 24+ hours to be updated with the new images after a new release of Node.js, so if you’re upgrading Node.js in Kibana just after the official Node.js release, you have to check if the new images are present on Docker Hub. This is used to pull the relevant image from Docker Hub. ci/Dockerfile - The version is specified in the NODE_VERSION constant.

Node js update