yarn @angular/platform-browser-dynamic 17.0.0-next.2
v17.0.0-next.2

latest releases: 17.3.10, 18.0.0, 18.0.0-rc.3...
8 months ago

17.0.0-next.2 (2023-08-30)

animations

Commit Description
fix - 698c058e1c remove code duplication between entry-points (#51500)
fix - 18be804c03 remove unnecessary escaping in regex expressions (#51554)

common

Commit Description
fix - 86c5e34601 remove code duplication between entry-points (#51500)

compiler-cli

Commit Description
fix - de2550d988 correct incomplete escaping (#51557)
fix - 3bca9db4a5 remove unnecessary escaping in regex expressions (#51554)

core

Commit Description
fix - dbffdc09c2 avoid duplicated code between entry-points (primary, testing, rxjs-interop) (#51500)
fix - 45d2ded0ea correct incomplete escaping (#51557)
fix - 006577f39c handle hydration of view containers that use component hosts as anchors (#51456)
fix - 1423bfbf8f remove unnecessary escaping in regex expressions (#51554)
fix - 3a19d6b743 run afterRender callbacks outside of the Angular zone (#51385)
perf - 685d01e106 chain template instructions (#51546)

language-service

Commit Description
fix - 88b1575271 correct incomplete escaping (#51557)

platform-browser

Commit Description
feat - c340d6e044 enable removal of styles on component destroy by default (#51571)
feat - c5daa6ce77 expose EventManagerPlugin in the public API. (#49969)

router

Commit Description
fix - c62e680098 Remove deprecated Router properties (#51502)

Breaking Changes

platform-browser

  • REMOVE_STYLES_ON_COMPONENT_DESTROY default value is now true. This causes CSS of components to be removed from the DOM when destroyed. You retain the previous behaviour by providing the REMOVE_STYLES_ON_COMPONENT_DESTROY injection token.

    import {REMOVE_STYLES_ON_COMPONENT_DESTROY} from '@angular/platform-browser';
    ...
    providers: [{
      provide: REMOVE_STYLES_ON_COMPONENT_DESTROY,
      useValue: false,
    }]

router

  • The following Router properties have been removed from
    the public API:

    • canceledNavigationResolution
    • paramsInheritanceStrategy
    • titleStrategy
    • urlUpdateStrategy
    • malformedUriErrorHandler

    These should instead be configured through the provideRouter or
    RouterModule.forRoot APIs.

Don't miss a new platform-browser-dynamic release

NewReleases is sending notifications on new releases.