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

Modules and third-party dependencies

Deno uses ECMAScript modules and imports that are fully compatible with the browser. The path to a module is absolute, so it includes the file extension, which is also a standard in the browser world.

Deno takes the approach of being a browser for scripts quite seriously. One of the things it has in common with web browsers is that it deeply leverages URLs. They're one of the most flexible ways to share a resource and work beautifully on the web. Why not use them for module resolution? That's what browsers did.

The fact that the path for modules is absolute makes it possible not to depend on third-party entities such as npm, or complex module resolution strategies. With absolute imports, we can import code directly from GitHub, from a proprietary server, or even from a gist. The only requirement is that it has a URL.

This decision enables a completely decentralized module distribution to be used and makes module resolution inside...