Anil Singh | Code-sample.com

What’s coming up in Ivy? You can expect: 1.       Generated code that is easier to read and debug at runtime 2.       Faster re-build time 3.       Improved payload - applications size improvements 4.       Improved template type checking 5.       Great backward compatibility 6.       And so on What’s coming up in version 8.0? Explore this link... And Watch(Google I/O'18) about new in Angular 8

Ivy Rendering Engine -  The Ivy rendering engine is a new backwards-compatible Angular renderer main focused on the following. 1.               Speed Improvements 2.               Size Reduction 3.               Increased Flexibility The template functions for creating dynamically views are no longer nested functions inside each other. Now we use for loops that are nested inside other loops. Stayed In formed - Angular 7 Interview Questions Example: function AppComponent ( rf : RenderFlags , ctx : AppComponent ) { function ulTemplateFun ( rf1 : RenderFlags , ctx0 : any ) { function liTemplateFun ( rf1 : RenderFlags , ctx1 : any ) {...}   } } No longer create multiple functions instances for loops that are nested inside other loops. Example: ...

The ngcc Angular node_module compatibility compiler - The ngcc is a tool which " upgrades " node_module compiled with non-ivy ngc into ivy compliant format. This compiler will convert node_modules compiled with Angular Compatibility Compiler (ngcc), into node_modules which appear to have been compiled with TSC compiler transformer ( ngtsc ) and this compiler conversions will allow such “ legacy ” packages to be used by the Ivy rendering engine . TSC transformer which removes and converts @Pipe , @Component , @Directive and @NgModule to the corresponding definePipe, defineComponent, defineDirective and defineInjector.