Angular 16.0.1–16.2.1 Is A Craftsmanship Effort
<h2>Angular 17 works begin. Let’s wrap up features introduced in Angular 16.0.1–16.2.1 before we’ll open popcorn for the new Angular major line!</h2>
<p>Somewhere around October 2022 we had some important <a href="https://tomaszs2.medium.com/angular-15-is-far-from-being-dead-3a9aa90fc9b6" rel="noopener">Angular 15</a> features released with some more in <a href="https://tomaszs2.medium.com/angular-15-1-0-makes-coding-a-bit-easier-8680dbdea436" rel="noopener">Angular 15.1.0</a>. In May, we’ve seen <a href="https://tomaszs2.medium.com/angular-16-release-kills-two-stones-with-one-bird-659022879573" rel="noopener">Angular 16</a> preceded by <a href="https://tomaszs2.medium.com/angular-16-rc2-the-revolution-is-near-d0f817a8933a" rel="noopener">Angular 16 RC2</a>.</p>
<p>Now, 3 months later, the work on 17.0.0 has started with the next.0 release made yesterday. So, before we’ll enjoy what the Angular team prepares for us in the following weeks, let’s look at what happened between Angular 16.0.0 and 16.2.1 released yesterday (2023–08–16):</p>
<p>During that time there were ten features and numerous bugfixes. But bugfixes are boring, so I’ll sum up the features for you since 16.0.1 to 16.2.1.</p>
<h1>1. HttpBackend Using Fetch API</h1>
<p><a href="https://angular.io/api/common/http/HttpBackend" rel="noopener ugc nofollow" target="_blank">HttpBackend </a>makes calls to backend ignoring interceptors. The <a href="https://github.com/angular/angular/pull/50247" rel="noopener ugc nofollow" target="_blank">new implementation</a> uses the Fetch API instead of polyfilled xhr2. No libraries needed anymore.</p>
<p>To enable it, you have to set it up explicitly as for now, because it’s in developer preview mode:</p>
<p><strong><a href="https://tomaszs2.medium.com/%EF%B8%8F-angular-16-0-1-16-2-1-is-a-craftsmanship-effort-337cf1435567">Read More</a></strong></p>