Ryan Dahl, the creator of the Node.js, has come up with a new runtime for JavaScript and TypeScript called  Deno. Given that its preview release had just been on May 12, 2020, its community has been growing in quite a number. The capability of Deno to fulfill the part of both runtime and package manager within a single executable seems intriguing. It contrasts with Node.js having TypeScript support out of the box and being secure by default.

I had a hard time watching “ 10 Things I Regret About Node.js” by Ryan Dahl in JSConf EU 2018 as he implied Deno to be better than Node.js in several aspects. I have been Node.js fanboy for years and it’s reasonable for me to believe Node.js isn’t going anywhere anytime soon. Nevertheless, I have decided to give Deno a shot.

With 68,000 plus GitHub stars in a matter of no time, Deno hype has become insurmountable, and breach of the peace in the Node.js community is obviously understandable.

This article aims to dive into this question from the perspective of a node.js developer. I will be using Deno for the very first time, and I hope it won’t disappoint. I will be writing everything I did and learned along the way. We will be building a simple but complete CRUD REST API server in Deno. I will be writing in TypeScript and will provide the project Github repo in the end.

#typescript #javascript #deno #nodejs #node