Angular v13 was released and available for download

Undoubtedly, this version was born under the Ivy-star, which is led to an expansion of Ivy-based features. Close cooperation between the developer's team and the Angular community is also bringing its fruits and leads, in turn, to provide a smooth, stable update process for your teams and projects.

There were a lot of words about fantastic Ivy abilities since v12 was released in May 2021. The Angular team was full of bright hopes, and apparently, they succeeded in landing some impactful changes in v13. They are sure of the excellent prospects for further optimization and improvement based on the Ivy engine

Don't even try to search for the View Engine in Angular v13. It's not here anymore. Angular v13 is finally rid of the View Engine and for today can reduce its reliance on ngcc. As a result, developer teams can expect a faster compilation. It will happen because of the metadata and summary files exclusion.

It is obvious that the changes made could not but affect the Angular Package Format (APF). The old output formats, including View Engine's specific metadata, were removed. The modern JS formats were implemented, which led to the creation of new libraries which no longer require the ngcc. Thus, library developers can count on faster execution and leaner package output.

Dynamical components' creation in previous Angular versions was another headache. You were doomed to generate tons of boilerplate code, which wasn't making your life easier. But now, the new API makes it possible to instantiate the component with ViewContainerRef.createComponent without making an associated factory. Thus, you are free not to use ComponentFactoryResolver in the constructor. Just compare creating components using previous versions and creating components via Angular v13 It’s just the beginning; the Angular team sees excellent prospects in the development of Ivy and promises a lot of other beautiful features in the future.

Vox populi Vox Dei - Voice of the people, the voice of God. According to the mass feedback from the community, the developer team permanently removed IE11 support from Angular v13. It may not be forever, but there are no plans to return to this issue shortly. Thus, you may use modern browser features to leverage native web APIs. Because of removing the IE-specific polyfills and code paths, apps will be smaller, load faster, and the need for differential loading will disappear. Your life will be better because of the improved APIs and built infrastructure from one side, and users will be happy because of the faster loading and an enhanced user experience from the other. These IE-specific polyfills will be automatically deleted as soon as you run ng update. If you still require IE11 support, you may keep using Angular v12 till November 2022.

Angular v13 supports the use of persistent build cache by default from now. This feature is available for the new v13 projects. Persistent build cache rises build speed up to 68%. In case you require to upgrade your old projects to v13, turn it on in configuration to angular.json: Check the documentation for more details.

Henceforth, ESBuild supports CSS source maps, optimize global CSS, and all style sheets. The optimization of the global scripts is done via terser.

For apps created with ng new, the default is RxJS 7.4. For existing RxJS v6.x applications, you should manually update using the npm install rxjs@7.4 command. Learn more at the summary on rxjs.dev. For Angular v13, it was added TypeScript 4.4 support. Check the TypeScript release blog for additional info.

In TestBed the DOM’s regular after-test cleaning expectantly leads to the faster, less memory-intensive, interdependent, and more optimized tests. This feature is used by default, but you may customize it. Here's how to configure it for the entire test suite using the TestBed.initTestEnvironment method: Also, you can configure it per each module independently via updating TestBed.configureTestingModule.

After the implementation of the Google Fonts, it's Adobe's Fonts turn. Thus, First Contentful Paint (FCP) is now enabled for everyone by default and improves your app performance. You should just again update ng, and it will be implemented into the system.

So, as you can see, Angular v13 made a big step ahead. In very close cooperation with the Angular developer's community, Angular guys have implemented various promising new features, so it's our turn to test it in the open sea.