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)

Revisiting the root provider scope

So far, we have discussed the following services in the Angular Academy application using the root scope provider:

  • SchoolsService: Retrieve information about the available schools.
  • CourseService: Retrieve information about the course.
  • ThemeService: Set and retrieve information about the current theme.

These services have served us well as singletons in the app so far – and marking the services for use with providedIn: 'root' via the Injectable decorator makes it pretty easy to use them for the standard use case. If you have been around since the early days of Angular, then you might have been accustomed to injecting services as dependencies in each specific module – for example, you might have been wondering why SchoolsService is not listed in the providers array from the schools module here:

@NgModule({
  declarations: [SchoolsComponent],
  imports: [CommonModule, GoogleMapsModule...