Shulou(Shulou.com)06/03 Report--

This article shows you how Angular12 abandons View Engine and replaces it with Ivy. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

The Angular team revealed that it plans to abandon the traditional compilation and rendering pipeline View Engine in version 12 and replace it with Ivy. However, this change does not require any action by developers; libraries that depend on View Engine can continue to work as expected through the compatible compiler ngcc.

According to the official blog, over the past year, Angular's new rendering and compilation pipeline, Ivy, has become the default experience for developers. Ivy can make Angular simpler, faster, and easier to maintain. When the team first enabled Ivy in Angular 9, they developed a compatibility compiler called ngcc that ensures backward compatibility with libraries that use View Engine. This will ensure that libraries that depend on it work properly even if the old compilation and rendering pipeline is deprecated.

In order to make a smooth transition from View Engine, Angular has developed an Ivy Library Distribution plan and shared it with the community as a RFC. The team collected a lot of feedback and released the preview implementation in Angular v11.2.

According to the Angular team, the reason for its decision to abandon View Engine is that most Angular developers have switched to Ivy. Currently, all Angular libraries are still in View Engine format. Because of the compatibility compiler, developers can use all of these libraries in Ivy applications and libraries; otherwise, View Engine libraries cannot rely on Ivy.

To ensure a smooth transition of libraries that rely on Angular frameworks and components, officials will continue to distribute them in View Engine format. But when Angular 13 is released and most third-party libraries already use Ivy, they also plan to transition Angular and its components.

The team pointed out that this change applies only to new applications and libraries, that no action needs to be taken on existing projects, and that developers will not be affected. For those who have libraries on which older applications or libraries depend, they recommend that you continue to distribute them in View Engine format and ensure that you do not choose to join the Ivy distribution until all dependent libraries are moved to Ivy.

The above is how Angular12 discards View Engine and replaces it with Ivy. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.