npm bundles have actually already had access to built-in Node.js modules such as fs (file system), course, process, and others through the runtime’s Node.js compatibility layer. In release 1.30, published January 25, these modules are exposed to Deno code via node: specifiers. For developers using code with both Deno and Node.js, the node: plan will operate in both runtimes. Deno has been positioned as a more protected option to Node.js, which has actually leveraged npm.Also in Deno 1.30, it now is possible to directly use a deno.json file as an import map, constituting what advocates referred to as a significant upgrade to the configuration file. Previously, it was possible to inform Deno where to search for an import map file by defining the importMap secret with a path to the import map file. This approach meant there were two files with configuration. To make things more concise, developers now can specify imports and scopes type in a setup file. Deno instantly will deal with the configuration file as an import map.Installation instructions for Deno can be discovered at deno.land.
Deno 1.30 likewise consists of more than 25 bug fixers pertinent to npm performance and Node-API. APIs also have actually been supported consisting of Deno.Listener.ref()and Deno.Listener.unref (). And deno fmt now can be formatted without semicolons.Deno 1.30 was preceded by Deno 1.29 in mid-December 2022, featuring npm compatibility enhancements and updates to the
REPL. 3 primarily bugfix point releases of Deno 1.30 likewise have been published given that the arrival of Variation 1.30. Copyright © 2023 IDG Communications, Inc. Source