Open Source Node.js Boosts Promising APIs


The Node.js project released version 17 of its open source JavaScript framework on October 19, providing developers and organizations they support with new features.

Part of the Linux Foundation’s OpenJS foundation, Node.js is one of the most widely used development frameworks by developers today. As is the case with many open source development efforts, Node.js offers both short and long term support versions. What is somewhat different with Node.js is that Long Term Support (LTS) releases are declared after a release is generally available, in an effort to eliminate bugs.

Node.js 17 is a short term release; Next week, Node.js 16 will be declared a long-term support version, with support until 2024.

“Node.js is really a community-driven project where they continually seek feedback while iterating and testing new features,” said Robin Ginn, Executive Director of the OpenJS Foundation. ITPro today. “Odd-numbered versions, like the current version 17, are a phased way to move the project forward before functionality arrives in the even long-term support version.”

New Promise JavaScript APIs arrive in Node.js 17

The notion of “promises “ is well defined in JavaScript, giving developers a way to configure a proxy for a value that is not immediately available but will be as the program continues to run.

In Node.js 17, there is a set of new Promise APIs that bring new functionality to developers.

“Adding a version of an API based on Promise allows developers to wait and simplify their code by removing potentially deep callback trees,” said Michael Dawson, chairman of the technical steering committee of Node.js and Senior Software Engineer at Red Hat. ITPro today.

The new version of Node.js also supports the new version OpenSSL 3. OpenSSL is an open source cryptographic library that is used for various security operations and is often used to help enable Transport Layer Security (TLS) for the web. application security.

Current versions of Node.js use OpenSSL 1.1.1, and the move to OpenSSL 3 was written to be relatively compatible with 1.1.1 but may require some tweaking for native modules, according to Dawson.

“The biggest impact is that some weaker algorithms and shorter key lengths will no longer be supported by default,” he said. “This may force applications to be modified to use better algorithms and / or longer key lengths. “

The path to adopting the Node.js 17 JavaScript framework

As to how and when organizations and developers will start adopting Node.js 17, Dawson said Node.js has a well-defined release process.

A new version is promoted to LTS every October, and each LTS version is supported for 30 months, he said. Organizations will vary in frequency of upgrade, with some organizations skipping alternative versions of LTS in order to only upgrade every two years.

“Typically, an organization selects its new target LTS version, tests its application with that version, and then deploys it,” Dawson said.

Source link

Leave A Reply

Your email address will not be published.