Angular v13 is now Available

Categories: Angular

Angular v13 is now Available

We’re back with the brand new release of Angular v13 to share with all of you! This latest release brings all sorts of updates and features to help your teams build great apps.

Get Angular v13 now by running ng update in your project. We also have an update guide available at update.angular.io to help teams get instructions on how to update their projects.

With each new release our goal is to find material ways to make Angular better. In this release, we’ve done that through expansion of Ivy-based features and optimizations, partnering with our excellent Angular community and continuing to provide a smooth, stable update process for your teams and projects.

Let’s start with a look at how we’re moving Angular forward with the power of Ivy.

Moving Angular rendering into the future

In the v12 release in May 2021 we talked about “Ivy Everywhere” and mentioned that there would be some important changes to Angular to support this initiative. We have been diligent in the pursuit of this and we’re extremely pleased to have landed some impactful changes in v13 as Ivy continues to open doors for optimizations and improvements.

State of View Engine

View Engine is no longer available in Angular as of v13. This is great news because Angular can continue to create Ivy-based features that bolster your productivity with the platform. Removing View Engine also means that Angular can reduce its reliance on ngcc (Angular compatibility compiler) in the future, and teams can look forward to faster compilation because metadata and summary files are no longer included.

Changes to the Angular Package Format (APF)

The Angular Package Format (APF) has been streamlined and modernized to better serve developers. To streamline the APF in v13 we’ve removed older output formats, including View Engine specific metadata.

To modernize it, we’ve standardized on more modern JS formats such as ES2020. Libraries built with the latest version of the APF will no longer require the use of ngcc. As a result of these changes library developers can expect leaner package output and faster execution.

We’ve also updated the APF to support Node Package Exports. This will help developers from inadvertently relying on internal APIs that may change.

End of IE11 support

We heard your feedback and worked to pave a path forward with the removal of IE11 support in Angular v13.

Removing IE11 support allows Angular to leverage modern browser features such as CSS variables and web animations via native web APIs. What’s more is that apps will be smaller and load faster because we can remove IE specific polyfills and code paths. It also removes the need for differential loading. Developers will benefit from improved APIs and build infrastructure while application users will benefit from faster loading and an improved user experience.

Running ng update will automatically drop these IE-specific polyfills and reduce bundle size during project migration.

Thanks to everyone who participated in the request for comments (RFC). Developers who still need to support IE11 users for existing projects can continue to use Angular v12 and it will be supported until November 2022.