{"id":1491,"date":"2023-09-21T05:00:00","date_gmt":"2023-09-21T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1491"},"modified":"2023-09-15T14:59:54","modified_gmt":"2023-09-15T21:59:54","slug":"what-is-the-ivy-engine","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/what-is-the-ivy-engine\/","title":{"rendered":"What is the Ivy engine?"},"content":{"rendered":"\n

You’ve probably heard about the Ivy engine<\/a> if you’ve been working with Angular for some time. Ivy is the code name of Angular’s current compilation and rendering pipeline.<\/p>\n\n\n\n

Before Ivy, Angular used a two-step process: Building a project would compile all Typescript code to Javascript. Then HTML templates would get compiled at runtime in the browser, using a second compiler called the View Engine<\/a>. This was done for performance reasons in the past, but the toolchain and the framework evolved for much better performance using the Ivy Engine.<\/p>\n\n\n\n

View Engine was deprecated in version 9 and removed from the framework in version 13. Ivy is the only option now and results in:<\/p>\n\n\n\n