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

Configuring the application for deployment

We now have an application that, when code is pushed to git, starts the process of building an image and deploying it. Our application currently gets deployed but it's not actually working, and this is happening because it is lacking configuration.

The first thing you probably noticed is that our application is always loading the configuration file from development, config.dev.yml, and it shouldn't.

When we first implemented this, we thought that different environments would have different configurations, and we were right. At the time, we didn't need to have configurations for more than one environment, and we used dev as a default. Let's fix that.

Remember that when we created the function that loads the configuration, we explicitly used an argument for the environment? We didn't use it at the time, but we left a default value.

Look at the following code snippet from src/config/index.ts:

export async...