@angular/platform-browser-dynamic

Explore Angular v19 with a blog post from the Angular team: blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• breaking

  this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• breaking

  Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.

  • ng update for v19 will take care of this automatically.

• breaking

  TypeScript versions less than 5.5 are no longer supported.

• breaking

  Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of
    the change detection process instead of as a microtask. Depending on the
    specifics of application/test setup, this can result in them executing
    earlier or later (or requiring additional test steps to trigger; see below
    examples).

  • effects which are triggered during change detection (e.g. by input
    signals) run earlier, before the component's template.

• breaking

  ExperimentalPendingTasks has been renamed to PendingTasks.

• breaking

  The autoDetect feature of ComponentFixture will now
  attach the fixture to the ApplicationRef. As a result, errors during
  automatic change detection of the fixture be reported to the ErrorHandler.
  This change may cause custom error handlers to observe new failures that were previously unreported.

• breaking

  createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content
    of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
  

• breaking

  Errors that are thrown during ApplicationRef.tick
  will now be rethrown when using TestBed. These errors should be
  resolved by ensuring the test environment is set up correctly to
  complete change detection successfully. There are two alternatives to
  catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger
    it synchronously and expect the error. For example, a jasmine test
    could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()

  • TestBed will reject any outstanding ComponentFixture.whenStable promises. A jasmine test,
    for example, could write expectAsync(fixture.whenStable()).toBeRejected().

  As a last resort, you can configure errors to not be rethrown by
  setting rethrowApplicationErrors to false in TestBed.configureTestingModule.

• breaking

  The timers that are used for zone coalescing and hybrid
  mode scheduling (which schedules an application state synchronization
  when changes happen outside the Angular zone) will now run in the zone
  above Angular rather than the root zone. This will mostly affect tests
  which use fakeAsync: these timers will now be visible to fakeAsync
  and can be affected by tick or flush.

• breaking

  The deprecated factories property in KeyValueDiffers has been removed.

elements

• breaking

  As part of switching away from custom CD behavior to the
  hybrid scheduler, timing of change detection around custom elements has
  changed subtly. These changes make elements more efficient, but can cause
  tests which encoded assumptions about how or when elements would be checked
  to require updating.

localize

• breaking

  The name option in the ng add @localize`` schematic has been removed in favor of the project option.

platform-browser

• breaking

  The deprecated BrowserModule.withServerTransition method has been removed. Please use the APP_ID DI token to set the application id instead.

router

• breaking

  The Router.errorHandler property has been removed.
  Adding an error handler should be configured in either
  withNavigationErrorHandler with provideRouter or the errorHandler
  property in the extra options of RouterModule.forRoot. In addition,
  the error handler cannot be used to change the return value of the
  router navigation promise or prevent it from rejecting. Instead, if you
  want to prevent the promise from rejecting, use resolveNavigationPromiseOnError.

• breaking

  The return type of the Resolve interface now includes
  RedirectCommand.

common

compiler

compiler-cli

core

elements

forms

http

language-service

localize

migrations

platform-browser

platform-server

router

service-worker