v19.0.0-next.7

19.0.0-next.7 (2024-09-25)

core

Commit	Description
	change effect() execution timing & no-op allowSignalWrites (#57874)
	mark signal-based query APIs as stable (#57921)
	migrate ExperimentalPendingTasks to PendingTasks (#57533)
	Ensure the ViewContext is retained after closure minification (#57903)

language-service

Commit	Description
	The suppress diagnostics option should work for external templates (#57873)

Breaking Changes

core

• Generally this PR has two implications:

  • 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.

  We've seen a few common failure cases:

  • Tests which used to rely on the Promise timing of effects now need to
    await whenStable() or call .detectChanges() in order for effects to
    run.

  • Tests which use faked clocks may need to fast-forward/flush the clock to
    cause effects to run.

  • effect()s triggered during CD could rely on the application being fully
    rendered (for example, they could easily read computed styles, etc). With
    the change, they run before the component's updates and can get incorrect
    answers. The recent afterRenderEffect() API is a natural replacement for
    this style of effect.

  • effect()s which synchronize with the forms system are particularly
    timing-sensitive and might need to adjust their initialization timing.

• ExperimentalPendingTasks has been renamed to
  PendingTasks.

v18.2.6

18.2.6 (2024-09-25)

v19.0.0-next.6

19.0.0-next.6 (2024-09-18)

compiler-cli

Commit	Description
	extended diagnostics not validating ICUs (#57845)

core

Commit	Description
	Add async run method on ExperimentalPendingTasks (#56546)
	mark input, output and model APIs as stable (#57804)
	stabilize @let syntax (#57813)
	Handle @let declaration with array when preparingForHydration (#57816)

migrations

Commit	Description
	introduce signal input migration as ng generate schematic (#57805)
	account for explicit standalone: false in migration (#57803)

v18.2.5

18.2.5 (2024-09-18)

compiler-cli

Commit	Description
	extended diagnostics not validating ICUs (#57845)

core

Commit	Description
	Handle @let declaration with array when preparingForHydration (#57816)

migrations

Commit	Description
	account for explicit standalone: false in migration (#57803)

v19.0.0-next.5

19.0.0-next.5 (2024-09-11)

core

Commit	Description
	allow passing undefined without needing to include it in the type argument of input (#57621)

v18.2.4

18.2.4 (2024-09-11)

compiler

Commit	Description
	produce less noisy errors when parsing control flow (#57711)

migrations

Commit	Description
	replace leftover modules with their exports during pruning (#57684)

v19.0.0-next.4

19.0.0-next.4 (2024-09-09)

compiler

Commit	Description
	produce less noisy errors when parsing control flow (#57711)

core

Commit	Description
	Add a schematics to migrate to standalone: false. (#57643)

migrations

Commit	Description
	migrate .pipe calls in outputs used in tests (#57691)
	remove complete calls for migrated outputs (#57671)
	replace .next usage on outputs (#57654)
	change imports to be G3 compatible (#57654)
	properly handle comments in output migration (#57691)
	replace leftover modules with their exports during pruning (#57684)

v19.0.0-next.3

19.0.0-next.3 (2024-09-04)

compiler

Commit	Description
	add diagnostic for unused standalone imports (#57605)

core

Commit	Description
	drop support for TypeScript 5.4 (#57577)
	initial version of the output migration (#57604)
	introduce afterRenderEffect (#57549)

elements

Commit	Description
	support output()-shaped outputs (#57535)

http

Commit	Description
	Dynamicaly call the global fetch implementation (#57531)

language-service

Commit	Description
	add code fix for unused standalone imports (#57605)
	add code reactoring action to migrate @Input to signal-input (#57214)
	allow code refactorings to compute edits asynchronously (#57214)

Breaking Changes

core

• • TypeScript versions less than 5.5 are no longer supported.

v18.2.3

18.2.3 (2024-09-04)

http

Commit	Description
	Dynamicaly call the global fetch implementation (#57531)

v19.0.0-next.2

19.0.0-next.2 (2024-08-28)

common

Commit	Description
	automatically use sizes auto in NgOptimizedImage (#57479)

compiler-cli

Commit	Description
	reduce duplicate component style resolution (#57502)

core

Commit	Description
	avoid leaking memory if component throws during creation (#57546)
	Do not bubble capture events. (#57476)
	fallback to default ng-content with empty projectable nodes. (#57480)
	Fix fixture.detectChanges with autoDetect disabled and zoneless (#57416)
	Schedulers run in zone above Angular rather than root (#57553)

elements

Commit	Description
	switch to ComponentRef.setInput & remove custom scheduler (#56728)

http

Commit	Description
	Dynamicaly call the global fetch implementation (#57531)

router

Commit	Description
	Do not unnecessarily run matcher twice on route matching (#57530)

upgrade

Commit	Description
	Address Trusted Types violations in @angular/upgrade (#57454)

Breaking Changes

core

• 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.

  For example:

  // 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]] });

• 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.

elements

• 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.