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)
Section 1: Getting Familiar with Deno
Section 2: Building an Application
Section 3: Testing and Deploying

Adding users to the application

We currently have the first endpoint running and listing all the museums in the application, but we're still far from meeting the final requirements.

We want to add users so that it is possible to register, log in, and interact with the application with an identity.

We'll start by creating the object that will define the user, and then proceed into the business logic to create and store it. After this, we'll create endpoints that will allow us to interact with the application via HTTP, thus allowing users to register.

Creating the user module

We currently have what we can call a single "module" in the application: the museums module. Everything that is related to museums is there, from controllers to repositories, object definitions, and so on. This module has one single interface, which is its index.ts file.

We did this so that we have the freedom of working inside the module while maintaining its external API...