async/await, which Deno takes into account. Since Deno is designed to work not only for small but also complex use cases where type checking becomes important, it supports TypeScript without additional tooling and its standard modules are written in TypeScript as well.
For the occasion of Deno’s first major release, we interviewed Node.js and Deno developer Ryan Dahl to find out about the main differences between the runtimes:
Deno uses a radically simple module system where modules and URLs are in one-to-one correspondence. Furthermore, Deno can execute TypeScript code out of the box. These two features have the effect of greatly simplifying the developer workflow. Deno is stricter with security than Node. […] Generally, Deno acts more like a web browser – it is, in essence, a web browser for command-line scripts.
If you want to dig deeper into 10 points Dahl regrets about Node, you can watch this video of his talk at JSConf EU:
Deno is available as a single executable with no dependencies. It can, for example, be downloaded via PowerShell (
iwr https://deno.land/x/install/install.ps1 -useb | iex), Chocolatey (
choco install deno), Scoop (
scoop install deno), or as a binary from GitHub.
See the Deno 1.0 release post by Ryan Dahl, Bert Belder, and Bartek Iwańczuk for further details.