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

Extracting configuration and secrets

Any application, independent of its dimension, will have configuration parameters. By looking at the application we've been building in the previous chapters, even if we look at the simplest version of them all—the Hello World web server—we'll find configuration values, such as the port value.

It's also not a coincidence that we're sending a full object called configuration inside the createServer function, the function that starts up the web server. At the same time, we also have a couple of values that we know should be secret in the application. They're currently living in the code base, as it's been working for our purpose (which is learning), but we want to change it.

We're thinking of things such as the JSON Web Token (JWT) encryption keys, or the MongoDB credentials. Those are definitely not things you want to check out into your version control system. This is what this section is about...