Book Image

Accelerating Angular Development with Ivy

By : Lars Gyrup Brink Nielsen, Mateus Carniatto, Jacob Andresen
Book Image

Accelerating Angular Development with Ivy

By: Lars Gyrup Brink Nielsen, Mateus Carniatto, Jacob Andresen

Overview of this book

Angular Ivy is the latest rendering engine and compiler introduced in Angular. Ivy helps frontend developers to make their Angular applications faster, better optimized, and more robust. This easy-to-follow guide will help you get to grips with the new features of Angular Ivy and show you how to migrate your Angular apps from View Engine to Ivy. You'll begin by learning about the most popular features of Angular Ivy with the help of simple stand-alone examples and realize its capabilities by working on a real-world application project. You'll then discover strategies to improve your developer workflow through new debugging APIs, testing APIs, and configurations that support higher code quality and productive development features. Throughout the book, you'll explore essential components of Angular, such as Angular Component Dev Kit (CDK), Ahead-of-time (AOT) compilation, and Angular command line interface (CLI). Finally, you'll gain a clear understanding of these components along with Angular Ivy which will help you update your Angular applications with modern features. By the end of this Angular Ivy book, you will learn about the core features of Angular Ivy, discover how to migrate your Angular View Engine application, and find out how to set up a high-quality Angular Ivy project.
Table of Contents (14 chapters)

Using the Angular Compatibility Compiler

In some Angular version 9 releases, we had to run the Angular Compatibility Compiler manually before building, testing, or serving our Angular Ivy application. In later releases, this changed so that the Angular CLI triggers the Angular Compatibility Compiler as needed.

It is still possible to run the Angular Compatibility Compiler manually. In fact, this allows for fine-tuning it to optimal compilation speed.

The Angular Compatibility Compiler needs to run at least once before any of the following:

  • Starting a development server
  • Executing automated tests
  • Building our application

Every time we install a new version of an Angular library or an additional Angular library from a package registry, we must run the Angular Compatibility Compiler again.

Consider running the Angular Compatibility Compiler as part of your Git repository's postinstall hook. When using this technique, we do not have to wait the next...