Ivy, Angular's new rendering and compilation pipeline, has a significant impact on (re)build times, offering improvements in several key areas:
Incremental Builds and Locality
Ivy's architecture is designed around the principle of locality, which means that each component is compiled with its own set of instructions, independent of the rest of the application. This allows for incremental builds where only the components that have changed need to be recompiled, rather than the entire application. This targeted recompilation greatly speeds up incremental build times, as developers do not have to wait for the entire application to rebuild when making changes to a single component[3][4].
Faster Re-compilation Times
With Ivy, developers have observed significant improvements in recompilation times. For instance, after upgrading to Angular 8.2, recompilation times improved, and the Ivy compiler managed to further reduce these times by 30-40%. This means that the time it takes to reflect code changes during development is noticeably reduced, enhancing the overall development experience[1].
Reduced Overhead for Libraries
Ivy also affects the build time by reducing the overhead associated with compiling libraries. With the introduction of the ngcc (Angular compatibility compiler), libraries that were originally compiled with the View Engine can be made compatible with Ivy. This process is faster in Angular 9.1 compared to Angular 9.0, and it is expected that once the migration period is over, the need for ngcc will diminish, further improving build times[1][2].
Bundle Size and Lazy Loading
Ivy has been shown to produce smaller bundles due to its tree-shaking capabilities, which remove unused code. Smaller bundles translate to faster loading times for users. Additionally, Ivy's handlin...
