TLDR; In v12, we’ll deprecate our legacy compilation and rendering pipeline called View Engine. This change will not require any action by developers. Libraries dependent on View Engine will continue to work as expected via our compatibility compiler _ngcc_. If you’re a library author or interested in understanding technical details, please continue reading the sections below.

Angular’s new rendering and compilation pipeline, Ivy, has been the developers’ default experience for the past year. To ensure interoperability with the old pipeline, we maintain compatibility layers that have implications on development experience. In this post, you’ll learn our plan for moving away from the legacy compiler towards faster compilation and simplicity.

Ivy has been a multi-year effort to make Angular simpler, faster, and easier to maintain. We’ve been fine-tuning the balance between static checks and dynamic constructs to ensure Angular continues to provide type checking, efficient build-time optimizations, and fast change detection.

Starting with version 9, we enabled Ivy for all-new Angular applications and provided a smooth, automated update path. To ensure backward compatibility of applications with libraries using the previous rendering and compilation pipeline (View Engine), we developed a compatibility compiler called ngcc.You’ve probably noticed ngcc run after you create a new project or install a dependency.

Running the Angular compatibility compiler

#angularjs #angular #angular-12