@angular/upgrade - npm Package Versions

published 17.3.11 • 6 months ago

18.1.0-next.0

published 18.1.0-next.0 • 6 months ago

18.0.1

published 18.0.1 • 6 months ago

Changelog

18.0.1 (2024-05-29)

compiler

| Commit | Type | Description | | -- | -- | -- | | 419ffa2026 | fix | optimize track function that only passes $index (#55872) |

compiler-cli

| Commit | Type | Description | | -- | -- | -- | | 4c7efc005a | fix | interpolatedSignalNotInvoked diagnostic for class, style, attribute and animation bindings (#55969) |

core

| Commit | Type | Description | | -- | -- | -- | | 4e6ea0e19c | fix | handle elements with local refs in event replay serialization logic (#56076) | | d73a0175cb | fix | link errors to ADEV (#55554) | | 985a215b10 | fix | typo in zoneless warning (#55974) |

migrations

| Commit | Type | Description | | -- | -- | -- | | ba85d08158 | fix | handle empty ngSwitchCase (#56105) |

17.3.10

published 17.3.10 • 6 months ago

Changelog

17.3.10 (2024-05-22)

18.0.0

published 18.0.0 • 6 months ago

Changelog

Blog post "Angular v18 is now available".

18.0.0 (2024-05-22)

Breaking Changes

animations

Deprecated matchesElement method has been removed from AnimationDriver as it is unused.

common

The deprecated isPlatformWorkerUi and isPlatformWorkerApp have been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.

compiler

Angular only supports writable expressions inside of two-way bindings.

compiler-cli

- Angular no longer supports TypeScript versions older than 5.4.

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
ComponentFixture.whenStable now matches the ApplicationRef.isStable observable. Prior to this change, stability of the fixture did not include everything that was considered in ApplicationRef. whenStable of the fixture will now include unfinished router navigations and unfinished HttpClient requests. This will cause tests that await the whenStable promise to time out when there are incomplete requests. To fix this, remove the whenStable, instead wait for another condition, or ensure HttpTestingController mocks responses for all requests. Try adding HttpTestingController.verify() before your await fixture.whenStable to identify the open requests. Also, make sure your tests wait for the stability promise. We found many examples of tests that did not, meaning the expectations did not execute within the test body.

In addition, ComponentFixture.isStable would synchronously switch to true in some scenarios but will now always be asynchronous.
Angular will ensure change detection runs, even when the state update originates from outside the zone, tests may observe additional rounds of change detection compared to the previous behavior.

This change will be more likely to impact existing unit tests. This should usually be seen as more correct and the test should be updated, but in cases where it is too much effort to debug, the test can revert to the old behavior by adding provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly}) to the TestBed providers.

Similarly, applications which may want to update state outside the zone and not trigger change detection can add provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly}) to the providers in bootstrapApplication or add schedulingMode: NgZoneSchedulingMode.NgZoneOnly to the BootstrapOptions of bootstrapModule.
When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.
async has been removed, use waitForAsync instead.
The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.
The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
Newly created and views marked for check and reattached during change detection are now guaranteed to be refreshed in that same change detection cycle. Previously, if they were attached at a location in the view tree that was already checked, they would either throw ExpressionChangedAfterItHasBeenCheckedError or not be refreshed until some future round of change detection. In rare circumstances, this correction can cause issues. We identified one instance that relied on the previous behavior by reading a value on initialization which was queued to be updated in a microtask instead of being available in the current change detection round. The component only read this value during initialization and did not read it again after the microtask updated it.
Testability methods increasePendingRequestCount, decreasePendingRequestCount and getPendingRequestCount have been removed. This information is tracked with zones.

http

By default we now prevent caching of HTTP requests that require authorization . To opt-out from this behaviour use the includeRequestsWithAuthHeaders option in withHttpTransferCache.

Example:
```
withHttpTransferCache({
  includeRequestsWithAuthHeaders: true,
})
```

platform-browser

Deprecated StateKey, TransferState and makeStateKey have been removed from @angular/platform-browser, use the same APIs from @angular/core.

platform-browser-dynamic

No longer used RESOURCE_CACHE_PROVIDER APIs have been removed.

platform-server

deprecated platformDynamicServer has been removed. Add an import @angular/compiler and replace the usage with platformServer
deprecated ServerTransferStateModule has been removed. TransferState can be use without providing this module.
deprecated useAbsoluteUrl and baseUrl been removed from PlatformConfig. Provide and absolute url instead.
Legacy handling or Node.js URL parsing has been removed from ServerPlatformLocation.

The main differences are;
- pathname is always suffixed with a /.
- port is empty when http: protocol and port in url is 80
- port is empty when https: protocol and port in url is 443

router

Guards can now return RedirectCommand for redirects in addition to UrlTree. Code which expects only boolean or UrlTree values in Route types will need to be adjusted.
This change allows Route.redirectTo to be a function in addition to the previous string. Code which expects redirectTo to only be a string on Route objects will need to be adjusted.
When a a guard returns a UrlTree as a redirect, the redirecting navigation will now use replaceUrl if the initial navigation was also using the replaceUrl option. If this is not desirable, the redirect can configure new NavigationBehaviorOptions by returning a RedirectCommand with the desired options instead of UrlTree.
Providers available to the routed components always come from the injector heirarchy of the routes and never inherit from the RouterOutlet. This means that providers available only to the component that defines the RouterOutlet will no longer be available to route components in any circumstances. This was already the case whenever routes defined providers, either through lazy loading an NgModule or through explicit providers on the route config.
Providers available to the routed components always come from the injector heirarchy of the routes and never inherit from the RouterOutlet. This means that providers available only to the component that defines the RouterOutlet will no longer be available to route components in any circumstances. This was already the case whenever routes defined providers, either through lazy loading an NgModule or through explicit providers on the route config.

Deprecations

common

getCurrencySymbol, getLocaleCurrencyCode, getLocaleCurrencyName, getLocaleCurrencySymbol, getLocaleDateFormat, getLocaleDateTimeFormat, getLocaleDayNames, getLocaleDayPeriods, getLocaleDirection, getLocaleEraNames, getLocaleExtraDayPeriodRules, getLocaleExtraDayPeriods, getLocaleFirstDayOfWeek, getLocaleId, getLocaleMonthNames, getLocaleNumberFormat, getLocaleNumberSymbol, getLocalePluralCase, getLocaleTimeFormat, getLocaleWeekEndRange, getNumberOfCurrencyDigits

core

@Component.interpolation is deprecated. Use Angular's delimiters instead.

http

HttpClientModule, HttpClientXsrfModule and HttpClientJsonpModule

As mentionned, those modules can be replaced by provider function only.

animations

common

compiler

| Commit | Type | Description | | -- | -- | -- | | 91b007e58f | fix | add math elements to schema (#55631) | | 33d0102304 | fix | allow comments between connected blocks (#55966) | | 7fc7f3f05f | fix | capture all control flow branches for content projection in if blocks (#54921) | | a369f43fbd | fix | capture switch block cases for content projection (#54921) | | eb625d3783 | fix | declare for loop aliases in addition to new name (#54942) | | f824911510 | fix | For FatalDiagnosticError, hide the message field without affecting the emit (#55160) | | a040fb720a | fix | maintain multiline CSS selectors during CSS scoping (#55509) | | 39624c6b12 | fix | output input flags as a literal (#55215) | | eba92cfa55 | fix | prevent usage of reserved control flow symbol in custom interpolation context. (#55809) | | 7d5bc1c628 | fix | remove container index from conditional instruction (#55190) | | 4eb0165750 | fix | remove support for unassignable expressions in two-way bindings (#55342) | | e1650e3b13 | fix | throw error if item name and context variables conflict (#55045) |

compiler-cli

| Commit | Type | Description | | -- | -- | -- | | 5bd188a394 | feat | add partial compilation support for deferred blocks (#54908) | | b02b31a915 | feat | drop support for TypeScript older than 5.4 (#54961) | | 78188e877a | fix | add diagnostic if initializer API is used outside of an initializer (#54993) | | 69a83993b3 | fix | do not throw when retrieving TCB symbol for signal input with restricted access (#55774) | | 4f4f41016e | fix | dom property binding check in signal extended diagnostic (#54324) | | 7a16d7e969 | fix | don't type check the bodies of control flow nodes in basic mode (#55360) | | 8d93597a82 | fix | fix type narrowing of @if with aliases (#55835) | | 9b424d7224 | fix | preserve original reference to non-deferrable dependency (#54759) | | 694ba79cbf | fix | report cases where initializer APIs are used in a non-directive class (#54993) | | 6219341d26 | fix | report errors when initializer APIs are used on private fields (#54981) | | c04ffb1fa6 | fix | use switch statements to narrow Angular switch blocks (#55168) |

core

forms

http

language-service

migrations

| Commit | Type | Description | | -- | -- | -- | | f914f6a362 | feat | Migration schematics for HttpClientModule (#54020) | | 8459ee46cb | fix | handle more cases in HttpClientModule migration (#55640) | | c4b2f18709 | fix | migrate HttpClientTestingModule in test modules (#55803) | | bb4a4016a9 | fix | preserve existing properties in HttpClientModule migration (#55777) | | f93e5180be | fix | resolve multiple structural issues with HttpClient migration (#55557) |

platform-browser

platform-browser-dynamic

platform-server

| Commit | Type | Description | | -- | -- | -- | | 5674c644ab | fix | add nonce attribute to event record script (#55495) | | e71e869112 | fix | remove event dispatch script from HTML when hydration is disabled (#55681) | | 07ac017731 | refactor | remove deprecated platformDynamicServer API (#54874) | | e8b588d8b7 | refactor | remove deprecated ServerTransferStateModule API (#54874) | | 3b1967ca64 | refactor | remove deprecated useAbsoluteUrl and baseUrl from PlatformConfig (#54874) | | 2357d3566c | refactor | remove legacy URL handling logic (#54874) |

router

| Commit | Type | Description | | -- | -- | -- | | 4a42961393 | feat | withNavigationErrorHandler can convert errors to redirects (#55370) | | 8735af08b9 | feat | Add ability to return UrlTree with NavigationBehaviorOptions from guards (#45023) | | 87f3f27f90 | feat | Allow resolvers to return RedirectCommand (#54556) | | 2b802587f2 | feat | Allow Route.redirectTo to be a function which returns a string or UrlTree (#52606) | | 60f1d681e0 | fix | preserve replaceUrl when returning a urlTree from CanActivate (#54042) | | 3839cfbb18 | fix | Routed components never inherit RouterOutlet EnvironmentInjector (#54265) | | da906fdafc | fix | Routed components never inherit RouterOutlet EnvironmentInjector (#54265) |

service-worker

| Commit | Type | Description | | -- | -- | -- | | 3bc63eaaf3 | fix | avoid running CDs on controllerchange (#54222) | | e598634c10 | fix | remove controllerchange listener when app is destroyed (#55365) |

18.0.0-rc.3

published 18.0.0-rc.3 • 6 months ago

18.0.0-rc.2

published 18.0.0-rc.2 • 6 months ago

17.3.9

published 17.3.9 • 6 months ago

Changelog