| Commit | Type | Description | | -- | -- | -- | | 930af9dd26 | fix | Fix MockPlatformLocation events and missing onPopState implementation (#48113) |

forms

| Commit | Type | Description | | -- | -- | -- | | b342e55509 | fix | don't mutate validators array (#47830) | | a12a120272 | fix | FormBuilder.group return right type with shorthand parameters. (#48084) |

language-service

| Commit | Type | Description | | -- | -- | -- | | cc8b76ef7c | fix | correctly handle host directive inputs/outputs (#48147) | | a8c33bf931 | fix | update packages/language-service/build.sh script to work with vscode-ng-language-service's new Bazel build (#48120) |

router

| Commit | Type | Description | | -- | -- | -- | | e4309d57d8 | fix | correct type of nextState parameter in canDeactivate (#48038) | | 9baefd085f | fix | Ensure renavigating in component init works with enabledBlocking (#48063) | | fa5528fb5f | fix | restore 'history.state' on popstate even if navigationId missing (#48033) |

Special Thanks

Alan Agius, Andrew Scott, Bjarki, Bob Watson, Brooke, Derek Cormier, Dylan Hunn, George Kalpakas, Greg Magolan, Ikko Ashimine, Ivan Rodriguez, Jessica Janiuk, Joe Roxbury, Joey Perrott, Kristiyan Kostadinov, Matthieu Riegler, Mikhail Savchuk, Nebojsa Cvetkovic, Pawel Kozlowski, Volodymyr and Wooshaah

5.0.0

Diff

sosukesuzuki

published 5.0.0 • last year

Changelog

Source

15.0.0 (2022-11-16)

Blog post "Angular v15 is now available".

Breaking Changes

compiler

Keyframes names are now prefixed with the component's "scope name". For example, the following keyframes rule in a component definition, whose "scope name" is host-my-cmp:

@keyframes foo { ... }

will become:

@keyframes host-my-cmp_foo { ... }

Any TypeScript/JavaScript code which relied on the names of keyframes rules will no longer match.

The recommended solutions in this case are to either:
- change the component's view encapsulation to the None or ShadowDom
- define keyframes rules in global stylesheets (e.g styles.css)
- define keyframes rules programmatically in code.

compiler-cli

Invalid constructors for DI may now report compilation errors

When a class inherits its constructor from a base class, the compiler may now report an error when that constructor cannot be used for DI purposes. This may either be because the base class is missing an Angular decorator such as @Injectable() or @Directive(), or because the constructor contains parameters which do not have an associated token (such as primitive types like string). These situations used to behave unexpectedly at runtime, where the class may be constructed without any of its constructor parameters, so this is now reported as an error during compilation.

Any new errors that may be reported because of this change can be resolved either by decorating the base class from which the constructor is inherited, or by adding an explicit constructor to the class for which the error is reported.
Angular compiler option enableIvy has been removed as Ivy is the only rendering engine.

core

Angular no longer supports Node.js versions 14.[15-19].x and 16.[10-12].x. Current supported versions of Node.js are 14.20.x, 16.13.x and 18.10.x.
TypeScript versions older than 4.8 are no longer supported.
Existing iframe usages may have security-sensitive attributes applied as an attribute or property binding in a template or via host bindings in a directive. Such usages would require an update to ensure compliance with the new stricter rules around iframe bindings.
Existing iframe usages may have src or srcdoc preceding other attributes. Such usages may need to be updated to ensure compliance with the new stricter rules around iframe bindings.

forms

setDisabledState will always be called when a ControlValueAccessor is attached. You can opt-out with FormsModule.withConfig or ReactiveFormsModule.withConfig.

localize

- canParse method has been removed from all translation parsers in @angular/localize/tools. analyze should be used instead.
- the hint parameter in theparse methods is now mandatory.

router

Previously, the RouterOutlet would immediately instantiate the component being activated during navigation. Now the component is not instantiated until the change detection runs. This could affect tests which do not trigger change detection after a router navigation. In rarer cases, this can affect production code that relies on the exact timing of component availability.
The title property is now required on ActivatedRouteSnapshot
relativeLinkResolution is no longer configurable in the Router. This option was used as a means to opt out of a bug fix.

Deprecations

common

The DATE_PIPE_DEFAULT_TIMEZONE token is now deprecated in favor of the DATE_PIPE_DEFAULT_OPTIONS token, which accepts an object as a value and the timezone can be defined as a field (called timezone) on that object.

core

- The ability to pass an NgModule to the providedIn option for @Injectable and InjectionToken is now deprecated.
providedIn: NgModule was intended to be a tree-shakable alternative to NgModule providers. It does not have wide usage, and in most cases is used incorrectly, in circumstances where providedIn: 'root' should be preferred. If providers should truly be scoped to a specific NgModule, use NgModule.providers instead.
- The ability to set providedIn: 'any' for an @Injectable or InjectionToken is now deprecated.
providedIn: 'any' is an option with confusing semantics and is almost never used apart from a handful of esoteric cases internal to the framework.
The bit field signature of Injector.get() has been deprecated, in favor of the new options object.
The bit field signature of TestBed.inject() has been deprecated, in favor of the new options object.

router

The RouterLinkWithHref directive is deprecated, use the RouterLink directive instead. The RouterLink contains the code from the RouterLinkWithHref to handle elements with href attributes.

common

| Commit | Type | Description | | -- | -- | -- | | c0c7efaf7c | feat | add provideLocationMocks() function to provide Location mocks (#47674) | | 75e6297f09 | feat | add <link> preload tag on server for priority img (#47343) | | 4fde292bb5 | feat | Add automatic srcset generation to ngOptimizedImage (#47547) | | 9483343ebf | feat | Add fill mode to NgOptimizedImage (#47738) | | bdb5371033 | feat | add injection token for default DatePipe configuration (#47157) | | 449d29b701 | fix | Add fetchpriority to ngOptimizedImage preloads (#48010) | | 4f52d4e474 | fix | don't generate srcset if noopImageLoader is used (#47804) | | 3a18398d83 | fix | Don't warn about image distortion is fill mode is enabled (#47824) | | edea15f2c6 | fix | export the IMAGE_CONFIG token (#48051) | | 8abf1c844c | fix | fix formatting on oversized image error (#47188) | | ca7bf65933 | fix | rename rawSrc -> ngSrc in NgOptimizedImage directive (#47362) | | b3879dbf14 | fix | support density descriptors with 2+ decimals (#47197) | | fa4798095e | fix | update size error to mention 'fill' mode (#47797) | | 23f210c0ab | fix | warn if using supported CDN but not built-in loader (#47330) | | 945432e3fa | fix | Warn on fill ngOptimizedImage without height (#48036) |

compiler

| Commit | Type | Description | | -- | -- | -- | | 051f75648d | fix | scope css keyframes in emulated view encapsulation (#42608) | | 39b72e208b | fix | update element schema (#47552) | | 48b354a83e | fix | update element schema (#47552) |

compiler-cli

core

forms

| Commit | Type | Description | | -- | -- | -- | | a8569e3802 | feat | export forms utility functions: isFormArray, isFormGroup… (#47718) | | 96b7fe93af | fix | call setDisabledState on ControlValueAcessor when control is enabled (#47576) | | a99d9d67f3 | fix | don't mutate validators array (#47830) | | 2625dc1312 | fix | Improve a very commonly viewed error message by adding a guide. (#47969) | | ae29f98c20 | fix | Runtime error pages must begin with leading zero (#47991) |

http

language-service

localize

| Commit | Type | Description | | -- | -- | -- | | 400a6b5e37 | fix | add polyfill in polyfills array instead of polyfills.ts (#47569) | | b6fd814542 | fix | update ng add schematic to support Angular CLI version 15 (#47763) | | d36fd3d9e4 | refactor | remove deprecated canParse method from TranslationParsers (#47275) |

platform-server

| Commit | Type | Description | | -- | -- | -- | | 2908eba59c | fix | align server renderer interface with base renderer (#47868) |

router

Special Thanks

Alan Agius, AleksanderBodurri, Alex Castle, Alex Rickabaugh, Andrew Kushnir, Andrew Scott, Charles Lyding, Dylan Hunn, Ferdinand Malcher, George Kalpakas, Jeremy Elbourn, Jessica Janiuk, JiaLiPassion, Joey Perrott, JoostK, Kara Erickson, Kristiyan Kostadinov, Martin Probst, Matthias Weiß, Matthieu Riegler, Paul Gschwendtner, Pawel Kozlowski, Sabareesh Kappagantu, WD Snoeijer, angular-robot[bot], arturovt, ced, dario-piotrowicz, ivanwonder and jaybell

4.0.1

Diff

fisker

published 4.0.1 • 2 years ago

Changelog

Source

14.0.1 (2022-06-08)

bazel

forms

| Commit | Type | Description | | -- | -- | -- | | dde0b7f4b3 | fix | allow FormBuilder.group(...) to accept optional fields. (#46253) |

Special Thanks

Adrien Crivelli, Alan Agius, Alex Rickabaugh, Andrew Kushnir, Andrew Scott, Dylan Hunn, Fabrizio Fallico, George Kalpakas, Jelle Bruisten, JoostK, Kristiyan Kostadinov, Krzysztof Platis, Paul Gschwendtner, Phalgun Vaddepalli, San Leen, dario-piotrowicz, mgechev and wellWINeo

4.0.0

Diff

fisker

published 4.0.0 • 2 years ago

Changelog

Source

14.0.0 (2022-06-02)

Blog post "Angular v14 is now available".

Breaking Changes

animations

The AnimationDriver.getParentElement method has become required, so any implementors of this interface are now required to provide an implementation for this method. This breakage is unlikely to affect application developers, as AnimationDriver is not expected to be implemented in user code.

common

Adds new required class member that any implementors of the LocationStrategy will need to satisfy. Location does not depend on PlatformLocation anymore.

compiler

Keyframes names are now prefixed with the component's "scope name". For example, the following keyframes rule in a component definition, whose "scope name" is host-my-cmp:

@keyframes foo { ... }

will become:

@keyframes host-my-cmp_foo { ... }

Any TypeScript/JavaScript code which relied on the names of keyframes rules will no longer match.

The recommended solutions in this case are to either:
- change the component's view encapsulation to the None or ShadowDom
- define keyframes rules in global stylesheets (e.g styles.css)
- define keyframes rules programmatically in code.

core

Support for Node.js v12 has been removed as it will become EOL on 2022-04-30. Please use Node.js v14.15 or later.
TypeScript versions older than 4.6 are no longer supported.
Forms [email] input coercion

Forms [email] input value will be considered as true if it is defined with any value rather than false and 'false'.
Since Ivy, TestBed doesn't use AOT summaries. The aotSummaries fields in TestBed APIs were present, but unused. The fields were deprecated in previous major version and in v14 those fields are removed. The aotSummaries fields were completely unused, so you can just drop them from the TestBed APIs usage.

forms

Forms classes accept a generic.

Forms model classes now accept a generic type parameter. Untyped versions of these classes are available to opt-out of the new, stricter behavior.
objects with a length key set to zero will no longer validate as empty.

This is technically a breaking change, since objects with a key length and value 0 will no longer validate as empty. This is a very minor change, and any reliance on this behavior is probably a bug anyway.

http

Queries including + will now actually query for + instead of space. Most workarounds involving custom codecs will be unaffected. Possible server-side workarounds will need to be undone.
JSONP will throw an error when headers are set on a reques

JSONP does not support headers being set on requests. Before when a request was sent to a JSONP backend that had headers set the headers were ignored. The JSONP backend will now throw an error if it receives a request that has any headers set. Any uses of JSONP on requests with headers set will need to remove the headers to avoid the error.

platform-browser

This change may cause a breaking change in unit tests that are implicitly depending on a specific number and sequence of change detections in order for their assertions to pass.
This may break invalid calls to TransferState methods.

This tightens parameter types of TransferState usage, and is a minor breaking change which may reveal existing problematic calls.

router

The type of Route.pathMatch is now stricter. Places that use pathMatch will likely need to be updated to have an explicit Route/Routes type so that TypeScript does not infer the type as string.
When returning a Promise from the LoadChildrenCallback, the possible type is now restricted to Type<any>|NgModuleFactory<any> rather than any.
initialNavigation: 'enabled' was deprecated in v11 and is replaced by initialNavigation: 'enabledBlocking'.
The type of component on ActivatedRoute and ActivatedRouteSnapshot includes string. In reality, this is not the case. The component cannot be anything other than a component class.
- The type of initialUrl is set to string|UrlTree but in reality, the Router only sets it to a value that will always be UrlTree
- initialUrl is documented as "The target URL passed into the Router#navigateByUrl() call before navigation" but the value actually gets set to something completely different. It's set to the current internal UrlTree of the Router at the time navigation occurs.
With this change, there is no exact replacement for the old value of initialUrl because it was never intended to be exposed. Router.url is likely the best replacement for this. In more specific use-cases, tracking the finalUrl between successful navigations can also be used as a replacement.
Lazy loaded configs are now also validated once loaded like the initial set of routes are. Lazy loaded modules which have invalid Route configs will now error. Note that this is only done in dev mode so there is no production impact of this change.
When a guard returns a UrlTree, the router would previously schedule the redirect navigation within a setTimeout. This timeout is now removed, which can result in test failures due to incorrectly written tests. Tests which perform navigations should ensure that all timeouts are flushed before making assertions. Tests should ensure they are capable of handling all redirects from the original navigation.
Previously, resolvers were waiting to be completed before proceeding with the navigation and the Router would take the last value emitted from the resolver. The router now takes only the first emitted value by the resolvers and then proceeds with navigation. This is now consistent with Observables returned by other guards: only the first value is used.