Boost your development efficiency by learning about
design patterns in TypeScript
What you need for this book
It is possible to read through this entire book without installing anything. But it is recommended that you have a handy editor and TypeScript compiler installed to get your hands dirty. Please refer to Chapter 1, Tools and Frameworks, for the detailed preparation of tools, including Node.js, a TypeScript compiler, declaration manager, and a nice editor or IDE.
Though this book does not require the reader to have a knowledge of design patterns, it’s not a book that teaches basic TypeScript syntax. If you are not yet familiar with TypeScript,
please walk through the TypeScript Handbook before reading Chapter 2, The Challenge of Increasing Complexity.
Who this book is for
If you are a TypeScript developer, this book is for you. No knowledge of design patterns is required to read this book.
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in the text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: “Save the following code to file test.ts.”
A block of code is set as follows:
Any command-line input or output is written as follows:
$ tsc test.ts
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: “Without the necessary declaration files, the compiler would complain Cannot find module express.”