Book Image

Learning TypeScript 2.x - Second Edition

By : Remo H. Jansen
Book Image

Learning TypeScript 2.x - Second Edition

By: Remo H. Jansen

Overview of this book

TypeScript is an open source and cross-platform statically typed superset of JavaScript that compiles to plain JavaScript and runs in any browser or host. This book is a step-by-step guide that will take you through the use and benefits of TypeScript with the help of practical examples. You will start off by understanding the basics as well as the new features of TypeScript 2.x. Then, you will learn how to work with functions and asynchronous programming APIs. You will continue by learning how to resolve runtime issues and how to implement TypeScript applications using the Object-oriented programming (OOP) and functional programming (FP) paradigms. Later, you will automate your development workflow with the help of tools such as Webpack. Towards the end of this book, you will delve into some real-world scenarios by implementing some full-stack TypeScript applications with Node.js, React and Angular as well as how to optimize and test them. Finally, you will be introduced to the internal APIs of the TypeScript compiler, and you will learn how to create custom code analysis tools.
Table of Contents (17 chapters)

Why does the command line win?

You may have noticed that during this chapter, we have used the CLI a lot instead of visual tools. We have used the command-line terminal to perform many kinds of tasks:

  • Work with source control
  • Install dependencies
  • Run tasks
  • Test our code
  • Debug our code
  • Create projects

The CLI has always been popular but I remember that, a few years ago, I used to do some of these things using Visual tools. For example, I remember running unit tests in .NET applications using a visual test runner for NUnit (a unit testing library for .NET applications). You might be wondering why we stopped using the visual tool and went back to the command line like in the early days?

I believe that the CLI wins for two main reasons:

  • Our software development teams have become much more diverse
  • Our software development methodologies have evolved toward automation

Our software...