Book Image

Learn React with TypeScript 3

By : Carl Rippon
Book Image

Learn React with TypeScript 3

By: Carl Rippon

Overview of this book

React today is one of the most preferred choices for frontend development. Using React with TypeScript enhances development experience and offers a powerful combination to develop high performing web apps. In this book, you’ll learn how to create well structured and reusable react components that are easy to read and maintain by leveraging modern web development techniques. We will start with learning core TypeScript programming concepts before moving on to building reusable React components. You'll learn how to ensure all your components are type-safe by leveraging TypeScript's capabilities, including the latest on Project references, Tuples in rest parameters, and much more. You'll then be introduced to core features of React such as React Router, managing state with Redux and applying logic in lifecycle methods. Further on, you'll discover the latest features of React such as hooks and suspense which will enable you to create powerful function-based components. You'll get to grips with GraphQL web API using Apollo client to make your app more interactive. Finally, you'll learn how to write robust unit tests for React components using Jest. By the end of the book, you'll be well versed with all you need to develop fully featured web apps with React and TypeScript.
Table of Contents (14 chapters)


Let's test our knowledge on React Router with the following questions:

  1. We have the following Route component that shows a list of customers:
<Route path="/customers" component={CustomersPage} />

Will the CustomersPage component render when the page is "/customers"?

  1. Will the CustomersPage component render when the page is "/customers/24322"?
  2. We only want the CustomersPage component to render when the path is "/customers". How can we change the attributes on Route to achieve this?
  3. What would be the Route component that could handle the "/customers/24322" path be? It should put "24322" in a route parameter called customerId.
  1. How can we catch paths that don't exist so that we can inform the user?
  2. How would we implement a search query parameter in CustomersPage? So, "/customers/?search=Cool...