Book Image

Deno Web Development

By : Alexandre Portela dos Santos
Book Image

Deno Web Development

By: Alexandre Portela dos Santos

Overview of this book

Deno is a JavaScript and TypeScript runtime with secure defaults and a great developer experience. With Deno Web Development, you'll learn all about Deno's primitives, its principles, and how you can use them to build real-world applications. The book is divided into three main sections: an introduction to Deno, building an API from scratch, and testing and deploying a Deno application. The book starts by getting you up to speed with Deno's runtime and the reason why it was developed. You'll explore some of the concepts introduced by Node, why many of them transitioned into Deno, and why new features were introduced. After understanding Deno and why it was created, you will start to experiment with Deno, exploring the toolchain and writing simple scripts and CLI applications. As you progress to the second section, you will create a simple web application and then add more features to it. This application will evolve from a simple 'hello world' API to a web application connected to the database, with users, authentication, and a JavaScript client. In the third section, the book will take you through topics such as dependency management, configuration and testing, finishing with an application deployed in a cloud environment. By the end of this web development book, you will become comfortable with using Deno to create, maintain, and deploy secure and reliable web applications.
Table of Contents (15 chapters)
1
Section 1: Getting Familiar with Deno
5
Section 2: Building an Application
10
Section 3: Testing and Deploying

Writing your first test in Deno

Before we start writing our test, it's important to remember a few things. The most important of them is, why are we testing?

There might be multiple answers to this question, but most of them will gesture toward guaranteeing that the code is working. You might also say that you use them so that you have flexibility when it comes to refactoring, or that you value having short feedback cycles when it comes to implementation – we can agree to both of these. Since we didn't write a test before implementing these features, the latter doesn't apply too much to us.

We'll keep these objectives in mind throughout this chapter. In this section, we'll write our first test. We'll use the application we wrote in the previous chapters and add tests to it. We'll write two types of tests: integration and unit tests.

Integration tests will test how different components of the application interact. Unit tests test layers...