Book Image

Hands-On TypeScript for C# and .NET Core Developers

By : Francesco Abbruzzese
5 (1)
Book Image

Hands-On TypeScript for C# and .NET Core Developers

5 (1)
By: Francesco Abbruzzese

Overview of this book

Writing clean, object-oriented code in JavaScript gets trickier and complex as the size of the project grows. This is where Typescript comes into the picture; it lets you write pure object-oriented code with ease, giving it the upper hand over JavaScript. This book introduces you to basic TypeScript concepts by gradually modifying standard JavaScript code, which makes learning TypeScript easy for C# ASP.NET developers. As you progress through the chapters, you'll cover object programming concepts, such as classes, interfaces, and generics, and understand how they are related to, and similar in, both ES6 and C#. You will also learn how to use bundlers like WebPack to package your code and other resources. The book explains all concepts using practical examples of ASP.NET Core projects, and reusable TypeScript libraries. Finally, you'll explore the features that TypeScript inherits from either ES6 or C#, or both of them, such as Symbols, Iterables, Promises, and Decorators. By the end of the book, you'll be able to apply all TypeScript concepts to understand the Angular framework better, and you'll have become comfortable with the way in which modules, components, and services are defined and used in Angular. You'll also have gained a good understanding of all the features included in the Angular/ASP.NET Core Visual Studio project template.
Table of Contents (16 chapters)

Optimizing bundles

When files must be organized in several different bundles, for instance, because the different bundles must be served in different web pages that need different JavaScript/TypeScript libraries, some optimization problems arise:

  • Some modules belongs to external libraries that will not be modified during the project's development. Thus, it makes no sense to process them during the frequent builds of the JavaScript/TypeScript project files. It makes more sense to organize them in separate bundles that are processed once and for all when all the library packages are installed.
  • If some modules are part of several bundles, it makes sense to factor them out into a separate bundle instead of duplicating them in all bundles. This way, the browser may cache them once and for all and they are not downloaded several times as parts of different bundles, thus reducing...