Book Image

Full-Stack React, TypeScript, and Node

By : David Choi
2 (1)
Book Image

Full-Stack React, TypeScript, and Node

2 (1)
By: David Choi

Overview of this book

React sets the standard for building high-performance client-side web apps. Node.js is a scalable application server that is used in thousands of websites, while GraphQL is becoming the standard way for large websites to provide data and services to their users. Together, these technologies, when reinforced with the capabilities of TypeScript, provide a cutting-edge stack for complete web application development. This book takes a hands-on approach to implementing modern web technologies and the associated methodologies for building full-stack apps. You’ll begin by gaining a strong understanding of TypeScript and how to use it to build high-quality web apps. The chapters that follow delve into client-side development with React using the new Hooks API and Redux. Next, you’ll get to grips with server-side development with Express, including authentication with Redis-based sessions and accessing databases with TypeORM. The book will then show you how to use Apollo GraphQL to build web services for your full-stack app. Later, you’ll learn how to build GraphQL schemas and integrate them with React using Hooks. Finally, you’ll focus on how to deploy your application onto an NGINX server using the AWS cloud. By the end of this book, you’ll be able to build and deploy complete high-performance web applications using React, Node, and GraphQL.
Table of Contents (22 chapters)
Section 1:Understanding TypeScript and How It Can Improve Your JavaScript
Section 2: Learning Single-Page Application Development Using React
Section 3: Understanding Web Service Development Using Express and GraphQL
Chapter 16: Adding a GraphQL Schema – Part II

Understanding how websites were built in the past

In this section, we will investigate the reasons for the creation of SPA-style programming by reviewing the original methods for designing and writing web pages. Having this knowledge will help us understand the reason for the shift to SPAs.

Originally, when the web was getting started, there was no JavaScript language. Initially, it was all just static HTML pages created to share documents among scientists. Once this document format and the internet became more popular, people realized that these documents needed improved styling methods to enhance communication. So, CSS was created and it became a standard for styling and the layout of HTML documents. Then, finally, the Netscape browser company decided the web needed a scripting language to make page content more dynamic, and they created JavaScript.

Despite these features, the original web was still very static in nature. When you entered a URL into your browser, you got back...