We have already briefly described the change detection mechanism of the framework. We said that compared to AngularJS, where it runs in the context of the "scope", in Angular 2 and later versions, it runs in the context of the individual components. Another concept we mentioned is the zones, which basically intercept all the asynchronous calls that we make using the browser APIs and provide execution context for the change detection mechanism of the framework. Zones fix the annoying problem that we have in AngularJS, where when we use APIs outside of Angular, we needed to explicitly invoke the digest loop.
In Chapter 1, Get Going with Angular and Chapter 2, The Building Blocks of an Angular Application, we discussed that the code that performs change detection over our components is being generated, either runtime (Just-in-Time) or as part of our build process (Ahead-of-Time). AoT compilation works great for environments with strict CSP (Content...
