{"id":359,"date":"2022-03-04T16:42:24","date_gmt":"2022-03-04T11:12:24","guid":{"rendered":"https:\/\/blogs.infosys.com\/digital-experience\/?p=359"},"modified":"2022-03-04T16:42:24","modified_gmt":"2022-03-04T11:12:24","slug":"angular-13-new-features","status":"publish","type":"post","link":"https:\/\/blogs.infosys.com\/digital-experience\/web-ui-ux\/angular-13-new-features.html","title":{"rendered":"Angular 13 New Features"},"content":{"rendered":"

This blog discusses the Angular framework feature changes release as part of Angular Version 13.<\/p>\n

Snippet from GitHub<\/strong><\/p>\n

The section mentions the key metrics (as of the date of writing this document) from GitHub. A probable indicator of platform adoption and stability.<\/p>\n

Star<\/strong>\u00a0 \u00a0– 79.4k\u00a0 \u00a0Fork<\/strong> – 20.9k\u00a0 \u00a0 \u00a0 Open Issues<\/strong> – 1.6k\u00a0 \u00a0Closed Issues<\/strong> – 21k<\/p>\n

Source URL<\/strong>–\u00a0 https:\/\/github.com\/angular\/angular<\/h6>\n

New Features<\/strong><\/em><\/h3>\n

IE 11 Support removal<\/span><\/h4>\n

Removal of IE 11 support enables angular to leverage modern browser features (for example \u2013 CSS variable, usage of modern browser API, etc.). Removal of IE 11 supports also resulted in the removal of IE 11 specific code from framework and polyfills, resulting in the smaller bundle and improved application performance.<\/p>\n

Note for Developers<\/strong> – This change is a breaking change for organizations supporting IE 11 browser.<\/p>\n

Reference URL<\/strong> –\u00a0https:\/\/github.com\/angular\/angular\/issues\/41840<\/a><\/p>\n

Component API update<\/span><\/h4>\n

One of the major changes in Angular 13 is the way the component is loaded dynamically. New component API has reduced a lot of boiler plate code. The new API uses ViewContainerRef.createComponent to dynamically load a component (without requiring an associated factory)<\/p>\n

Example<\/p>\n

\"\"<\/p>\n

View Engine Removal<\/span><\/h4>\n

Angular 13 mandates it to build application\/library using IVY engine i.e. no more you can use view engine as rendering engine it has to be IVY or partial-ivy for libraries.<\/p>\n

How does it impact?<\/p>\n

Angular 13 still supports libraries published with a view engine. For view engine libraries NGCC still exists. Change is seamless for the application developer. For example, while migrating from Angular 12 to 13 applications should still be able to consume libraries developed using the view engine.<\/p>\n

The change impacts the library developers. The libraries developed being Angular 13 and to be published to NPM needs to be published with Partial Ivy (recommended) or Fully Ivy option.<\/p>\n

Dependency Update<\/span><\/h4>\n

Angular 13 has a dependency on the upgraded version of RxJS, TypeScript & NodeJS.<\/p>\n