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.

Deno Web Development

Preface

What is Deno?

Now that we're familiar with evented languages, Node's history, and the reasons that led to Deno, we're in good shape to start writing some code.

The Toolchain

Now that we know enough about Deno, we're in a good place to write a few real applications with it. In this chapter, we'll be using no libraries as its primary purpose is to present the runtime APIs and the standard library.

The Runtime and Standard Library

Building a Web Application

At this point, we have laid the foundations for a web application with a structure that will enable us to add more functionalities as we proceed. As you might have guessed by the name of this chapter, we'll start this chapter by adding the middleware framework of our choice to the current web application, Oak.

Adding Users and Migrating to Oak

In the previous chapter, we added an HTTP framework to our application, heavily simplifying our code. After that, we added the concept of users to the application and developed the register endpoint. In its current state, our application is already storing a couple of things, with the small gotcha that it's storing it in memory. We'll tackle this specific issue in this chapter.

Adding Authentication and Connecting to the Database

In the previous chapter, we pretty much wrapped up our application's features. We added authorization and persistence, ending up with an application connected to a MongoDB instance. In this chapter, we'll focus on some known best practices that are standard in production applications: basic security practices and dealing with configuration.

HTTPS, Extracting Configuration, and Deno in the Browser

Testing &ndash; Unit and Integration

Deployment is a crucial part of any application. We might build a great application, follow best practices, and write tests, but at the end of the day, when it gets to the user, this is where it will prove its value. As we want this book to be a journey through all the different phases of an application, we'll use this chapter about application deployment to close the cycle.

Deploying a Deno Application

We've come a long way. We started by getting to know the basics of Deno and went on to building and deploying a complete application. By now, you should be comfortable with Deno and have a good awareness of the problems it solves. Hopefully, all the phases we've been through have helped clarify many questions you may have had about Deno.

Community Questions