harrytran998 / deno-web-development

Deno Web Development, Published by Packt

Getting started with Deno (https://deno.land/)

Published by PacktPub Authored by Alexandre Portela dos Santos

Write, test, maintain and deploy JavaScript and TypeScript applications using Deno.

Learn how to use Deno, the secure JavaScript and TypeScript runtime written in Rust, to write reliable web applications

---

This repository contains all the code snippets from the book, plus some more extensive examples and explanations. The chapter's list is available below.

The book

This book targets developers who want to leverage their JavaScript and TypeScript skills in a secure, simple, and modern runtime, using it for web development. Node.js knowledge is not required but recommended.

Deno

Deno is a JavaScript/TypeScript runtime with secure defaults and a great developer experience.

“Getting started with Deno” will introduce Deno’s primitives, its principles, and how developers can use it to build real-world applications. The book is divided into three main sections: introducing Deno, building an API from scratch, and testing and deploying a Deno application. The first chapters present the runtime and the motivations behind its creation. It explores some of the concepts introduced by Node, why many of them transitioned into Deno, and why new features were introduced. After getting comfortable with Deno and why it was created, the reader will start to experiment with Deno, exploring the toolchain, and writing simple scripts and CLI applications. As we transition in the second section of the book, the reader will start with a very simple web application and will slowly 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 meantime, topics like dependency management, configuration, testing, and application structure, among others will be addressed.

By the end of the read, the reader is comfortable in using Deno to create, maintain, and deploy secure and reliable web applications.

Author Bio

Alexandre is a software engineer passionate about products and startups. For the last 8+ years he's been working together with multiple companies, using technology as an enabler for ideas and businesses. With a big interest in education and getting people excited about technology, he makes sure he's always involved with people that are learning about it, being it via blog posts, books, open source contributions, or meetups. This is, by itself, a learning adventure that Alexandre loves to be a part of. Being a true believer that great software only happens through collaboration, ownership, and teams of great people, he strives to nurture those values in every project he works in.

Index

The book is composed of 10 chapters and 3 main sections. The sections are: Introduction to Deno, Building an application, Testing and Deploying. The chapters list and direct link to code is available below.

1. What is deno?
2. The toolchain (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch2/)
3. Runtime and standard library (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch3/)
4. Building a web application (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch4/)
5. Adding users and migrating to oak (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch5/)
6. Adding authentication and connecting to the database (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch6/)
7. HTTPS, extracting configuration and Deno on the browser (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch7/)
8. Testing - Unit and integration (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch8/)
9. Deploying a Deno application (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch9/)
10. What's next? (https://github.com/PacktPublishing/Deno-Web-Development/tree/master/ch10/)

Chapter that have multiple iterations of the same application have inside a sections folder with copies of the application at each state. It should be possible to have access to the code at a certain point in chapter.