Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Full-Stack React, TypeScript, and Node
  • Toc
  • feedback
Full-Stack React, TypeScript, and Node

Full-Stack React, TypeScript, and Node

By : David Choi
3.5 (18)
close
Full-Stack React, TypeScript, and Node

Full-Stack React, TypeScript, and Node

3.5 (18)
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)
close
1
Section 1:Understanding TypeScript and How It Can Improve Your JavaScript
5
Section 2: Learning Single-Page Application Development Using React
10
Section 3: Understanding Web Service Development Using Express and GraphQL
19
Chapter 16: Adding a GraphQL Schema – Part II

Mocking

Mocking is simply replacing specific functionality in our test with default values. An example of mocking could be to only pretend to make a network call but instead return a hardcoded value. The reason we want to do this is we want to only test a single unit or a small piece of our code. By mocking some portions of our code that are not specific to what we are testing, we are avoiding confusion and making certain our test works consistently. For example, if we were trying to test input in our code, we wouldn't want a network call failure to affect the result of that test, because a network call has nothing to do with the input element specifically. When we want to do end-to-end testing or integration testing, we can worry about the network call as well. But that is a different animal from unit testing (in some teams, integration testing is handled by the QA team separately) and we won't cover it here. Now, when it comes to React components, testing-library actually...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete