Book Image

The TypeScript Workshop

By : Ben Grynhaus, Jordan Hudgens, Rayon Hunte, Matt Morgan, Vekoslav Stefanovski
5 (1)
Book Image

The TypeScript Workshop

5 (1)
By: Ben Grynhaus, Jordan Hudgens, Rayon Hunte, Matt Morgan, Vekoslav Stefanovski

Overview of this book

By learning TypeScript, you can start writing cleaner, more readable code that’s easier to understand and less likely to contain bugs. What’s not to like? It’s certainly an appealing prospect, but learning a new language can be challenging, and it’s not always easy to know where to begin. This book is the perfect place to start. It provides the ideal platform for JavaScript programmers to practice writing eloquent, productive TypeScript code. Unlike many theory-heavy books, The TypeScript Workshop balances clear explanations with opportunities for hands-on practice. You’ll quickly be up and running building functional websites, without having to wade through pages and pages of history and dull, dry fluff. Guided exercises clearly demonstrate how key concepts are used in the real world, and each chapter is rounded off with an activity that challenges you to apply your new knowledge in the context of a realistic scenario. Whether you’re a hobbyist eager to get cracking on your next project, or a professional developer looking to unlock your next promotion, pick up a copy and make a start! Whatever your motivation, by the end of this book, you’ll have the confidence and understanding to make it happen with TypeScript.
Table of Contents (16 chapters)
Preface

Promise Methods

In addition to the standard next and catch methods exposed by promises, there are a number of other convenience methods, such as all, allSettled, any, and race, that make working with promises nicer. How can they be used in the async/await world? They can actually work together quite nicely. For example, here is a use of Promise.all that employs then and catch. Given three promises, p1, p2, and p3:

Promise.all([p1, p2, p3])
  .then(values => console.log(values))
  .catch(e => console.error(e));

There isn't any kind of awaitAll operator, so if we want to execute our promises in parallel, we're still going to need to use Promise.all, but we can avoid chaining then and catch if we choose to:

try {
  const values = await Promise.all([p1, p2, p3]);
  console.log(values);
} catch (e) {
  console.error(e);
}

In this case, we might feel like the code isn't improved by the addition of await...