@angular/platform-browser

What are @angular/platform-browser's main functionalities?

import { BrowserModule } from '@angular/platform-browser';

@NgModule({
  imports: [BrowserModule],
  ...
})
export class AppModule { }

import { Component, HostListener } from '@angular/core';

@Component({...})
export class MyComponent {
  @HostListener('window:resize', ['$event'])
  onResize(event) {
    // Handle the browser resize event
  }
}

import { DomSanitizer } from '@angular/platform-browser';

@Component({...})
export class MyComponent {
  safeUrl;
  constructor(private sanitizer: DomSanitizer) {
    this.safeUrl = this.sanitizer.bypassSecurityTrustResourceUrl('https://example.com');
  }
}

17.0.5 (2023-11-29)

core

| Commit | Type | Description | | -- | -- | -- | | 6be88040d1 | fix | avoid stale provider info when TestBed.overrideProvider is used (#52918) | | dee50f1d78 | fix | inherit host directives (#52992) | | 07920d96d4 | fix | Reattached views that are dirty from a signal update should refresh (#53001) |

migrations

| Commit | Type | Description | | -- | -- | -- | | aab7fb8654 | fix | Add ngForTemplate support to control flow migration (#53076) | | dbd6f386ea | fix | allows colons in ngIf else cases to migrate (#53076) | | 5b9f896009 | fix | cf migration fix migrating empty switch default (#53237) | | 2b3d3b0fe1 | fix | CF migration log warning when collection aliasing detected in @for (#53238) | | dffeac8386 | fix | cf migration removes unnecessary bound ngifelse attribute (#53236) | | 00cb3339ba | fix | control flow migration formatting fixes (#53076) | | c22af72f75 | fix | fix off by one issue with template removal in CF migration (#53255) | | ba6d7fe018 | fix | fixes CF migration i18n ng-template offsets (#53212) | | 8f6affdd64 | fix | fixes control flow migration common module removal (#53076) | | 6ae408847c | fix | properly handle ngIfThen cases in CF migration (#53256) | | 0fcef65cea | fix | Update CF migration to skip templates with duplicate ng-template names (#53204) |

router

| Commit | Type | Description | | -- | -- | -- | | 91486aaf07 | fix | Resolvers in different parts of the route tree should be able to execute together (#52934) |

<a name="17.0.4"></a>