Member-only story
Angular 13 in Depth
Angular 13 is now available. Time to discover what’s new!
In this article, I’ll go over (almost) everything noteworthy in this new release. I’ll also highlight what’s changed around Angular, as I did with my previous articles about Angular 12, Angular 11, and Angular 10.
What’s new with Angular 13
If you’re looking for the bird-eye view, then here it is:
- IE11 is no longer supported
- Faster production builds (+68%)
- Persistent build cache by default: https://github.com/angular/angular-cli/issues/21545
- View Engine is gone
- New Angular Package Format (APF): https://angular.io/apf
- Simplified API to dynamically create components
- Minor improvements to forms type safety
- Improvements to Angular TestBed
- Accessibility (a11y) improvements to MDC-based Angular Material components
- TypeScript >=4.4.x
- RxJS >=7.4
If you want more, then check out the official release announcement.
And if you want all the details, then stay here with me! We’re going to dig much deeper into the release notes ✨.
IE11 is no longer supported
Angular 13 no longer supports Internet Explorer. I consider this to be one of the most important news.
By dropping support for Internet Explorer, Angular can finally make use of native Web browser features such as CSS variables and Web animations. Previously, Angular had to include polyfills to ensure retro-compatibility with IE.
This means that Angular is now lighter than before, and will load/execute faster (i.e., better UX!). Moreover, the Angular team can now focus on evergreen Web browsers, which will enable faster innovation cycles.
