Is Deno a Threat to Node?

Deno 1.0 was launched on May 13, 2020, by Ryan Dahl — the creator of Node

Kapil Raghuwanshi
May 15 · 5 min read
Image for post
Image for post
Image copyrights Deno team —

It’s been around for two years now. We’re hearing the term Deno, and the developer community, especially the JavaScript community, is quite excited since it’s coming from the author of Node, Ryan Dahl. In this article, we’ll discuss a brief history of Deno and Node along with their salient features and popularity.

Deno was announced at JSConf EU 2018 by Ryan Dahl in his talk “10 Things I Regret About Node.js.” In his talk, Ryan mentioned his regrets about the initial design decisions with Node.

JSConf EU 2018 — YouTube

In his JSConf presentation, he explained his regrets while developing Node, like not sticking with promises, security, the build system (GYP), package.jsonand node_modules, etc. But in the same presentation, after explaining all the regret, he launched his new work named Deno. It was in the process of development then.

But on 13th May 2020, around two years later, Deno 1.0 was launched by Ryan and the team (Ryan Dahl, Bert Belder, and Bartek Iwańczuk). So let’s talk about some features of Deno.

What Is Deno?

Deno is a JavaScript/TypeScript runtime with secure defaults and great developer experience. Deno is built on three pillars:

  1. Chrome V8 — JavaScript runtime engine
  2. Rust Programming language
  3. Tokio — As noted on GitHub, “a runtime for writing reliable, asynchronous, and slim applications”

Deno aims to be a productive and scripting environment for the modern programmer. Similar to Node, Deno emphasizes event-driven architecture, providing a set of non-blocking core IO utilities, along with their blocking versions.

Installation steps

Deno ships as a single executable with no dependencies. You can install it using the installers below.

Using Shell:

curl -fsSL | sh

Or using Homebrew:

brew install deno

See deno_install for more installation options.

A basic Hello-World program in Deno looks like the following (same as in Node):

console.log("Hello world");

We will try to compare the features of Deno with Node throughout the article. And in the end, we’ll try to find out whether or not it’s really a threat.

There is no doubt that Node is a hugely successful JavaScript runtime environment. Today, more than thousands of production builds are using Node. Another reason for this success is NPM, a package manager for the JavaScript runtime environment Node, which has millions of reusable libraries and packages for every JavaScript developer out there. Node is a decade old now: It was initially launched on May 27, 2009. On the other hand, Deno is relatively very new and still not used in production builds much. It can be used to create web servers like Node, perform scientific computations, etc.

Highlighted Features of Deno

  • Secure (No file, network, or environment access by default_
  • Ships only a single executable file
  • Say no to node_modules and package.json
  • TypeScript support out of the box


The program in Deno is executed in a secure sandbox (by default). Scripts cannot access the hard drive, open network connections, or make any other potentially malicious actions without permission. For example, the following runs a basic Deno script without any read/write/network permissions:

deno run index.ts

Explicit flags are required to expose corresponding permission:

deno run --allow-read --allow-net index.ts

Single executable file

Deno attempts to provide a standalone tool for quickly scripting complex functionality. Deno is a single file that can define arbitrarily complex behavior without any other tooling, so every library will be explicitly called and included in the program.

Module system

Here, we do not have any package.json or node_modules. Source files can be imported using a relative path, an absolute path, or a fully qualified URL of a source file. as shown below:

import { serve } from “";for await (const req of serve({ port: 8000 })) {  req.respond({ body: “Hello from Deno\n” });}

TypeScript support

TypeScript is an open-source programming language developed and maintained by Microsoft. TypeScript, in the end, transcompiles to JavaScript only. It is another popular language of recent times used heavily in the Angular Framework and React.js UI library. Deno supports TypeScript without additional tooling.

Deno is a new runtime for executing JavaScript and TypeScript outside of the web browser, like Node. But it’s important to understand that Deno is not an extension of Node — it’s completely a newly written implementation.

Slowly, Deno is also getting popular, like Node. You can see the popularity by Deno’s official twitter handle @deno_land with 11.5K followers and 50k+ stars on Github

Image for post
Image for post
Deno on GitHub

Limitations of Deno

  • Deno is not compatible with Node (NPM) packages. That’s a huge disappointment for the big JavaScript dev community.
  • Since it uses the TypeScript compiler internally to parse the code to plain JavaScript, it is still very slow comparatively.
  • It lags in HTTP server performance.

In the end, we can conclude that Node and Deno are two different JavaScript runtime environments altogether — so it’s better not to compare them. The choice depends on the given requirements. After looking at the gradually increasing popularity of Node among developers for a decade, I think it will be difficult for Deno to cover that in less time. But indeed, for new features, one can definitely try Deno. We will keep an eye on further developments with Deno and figure out more in the coming years. So, today we can make a statement that:

As of 2020, Deno is not at all a threat to Node.

Write your suggestions and feedbacks in the comment section below.

Read my other articles below and follow me on Medium here.

Let’s be connected on LinkedIn (@kapilraghuwanshi) and Twitter (@techygeeeky) for more such engaging Tech Articles and Tutorials.🤝

Better Programming

Advice for programmers.

Kapil Raghuwanshi

Written by

JavaScript Ecosystem Hacker🤠| Machine Learning Practitioner| Tech Author| Public Speaker| Let’s connect on LinkedIn @kapilraghuwanshi & Twitter (@techygeeeky)

Better Programming

Advice for programmers.

Kapil Raghuwanshi

Written by

JavaScript Ecosystem Hacker🤠| Machine Learning Practitioner| Tech Author| Public Speaker| Let’s connect on LinkedIn @kapilraghuwanshi & Twitter (@techygeeeky)

Better Programming

Advice for programmers.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store