With Deno, npm packages have already had access to built-in Node.js modules such as fs (file system), path, 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
<a href="https://nodejs.org/api/esm.html#urls" rel="nofollow">node:</a>
specifiers. For developers using code with both Deno and Node.js, the node: scheme will work in both runtimes. Deno has been positioned as a more secure alternative to Node.js, which has leveraged npm.