A new month, a new Deno release – version 1.16 of the runtime for JavaScript and TypeScript has appeared. The Deno team has added some new features, including a new signal listener API and a build tool for Deno modules. The only breaking change is the removal of ReadableStream.getIterator.
Deno-Module in npm
The new system appears with Deno 1.16 dnt (Deno to Node Transform). The build tool is used to publish modules written in Deno as npm packages for use with Node.js. Although dnt is still in a very early stage, it comes in the sample project deno_license_checker already in use, which can be installed as follows:
npm install -g @kt3k/license-checker
Also working on the compatibility mode with Node.js (--compat) continues, but the Deno team has no news to announce at this time. Deno comes from the same developer pen as Node.js, which was also launched by Ryan Dahl.
Signal listener API and new JSX transformations
Less than a month ago, the plan was that Deno.signal()-API to stabilize in Deno 1.16. The Deno team has obviously rejected this plan, because instead it is introducing an equally unstable new signal listener API as their successor:
const listener = () => { console.log("SIGTERM!");
}; // Starts listening to SIGTERM
Deno.addSignalListener("SIGTERM", listener); // Stops listening to SIGTERM
Deno.removeSignalListener("SIGTERM", listener);
Further innovations
Deno 1.16 allows the use of the new JSX transformations that found their way into the JavaScript library with React 17. They revised the JSX Transform API and brought with them the ability to automatically import the JSX runtime library. In addition, the JavaScript engine V8 contained in Deno has been increased to version 9.7 and is thus two versions higher than before.
The most important changes in Deno 1.16 highlights a blog post. All details can be found in the release notes on GitHub.
(May)
Disclaimer: This article is generated from the feed and not edited by our team.
from WordPress https://ift.tt/3Hcd3Il
via IFTTT
No comments:
Post a Comment