| 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) |

8.0.0

Diff

fisker

published 8.0.0 • 3 weeks ago

Changelog

Source

18.0.0 (2024-05-22)

Blog post "Angular v18 is now available".

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) |

7.0.1

Diff

fisker

published 7.0.1 • 2 months ago

Changelog

Source

17.0.1 (2023-11-08)

http

| Commit | Type | Description | | -- | -- | -- | | 5c6f3f8ec0 | fix | Don't override the backend when using the InMemoryWebAPI (#52425) |

migrations

| Commit | Type | Description | | -- | -- | -- | | 70d30c28e0 | fix | Add support for ng-templates with i18n attributes (#52597) | | 4f125c5f9a | fix | Switches to multiple passes to fix several reported bugs (#52592) |

Web Frameworks: the internet frontier. These are the voyages of the framework Angular. Its continuing mission: To explore strange, new technologies. To seek out new users and new applications. To boldly go where no web framework has gone before.

In honor of v17.0.1

                                                  ______
                                     ___.--------'------`---------.____
                               _.---'----------------------------------`---.__
                             .'___=]===========================================
,-----------------------..__/.'         >--.______        _______.---'
]====================<==||(__)        .'          `------'
`-----------------------`' ----.___--/
     /       /---'                 `/
    /_______(______________________/
    `-------------.--------------.'
                   \________|_.-'

Live long and prosper 🖖🏻

7.0.0

Diff

fisker

published 7.0.0 • 3 months ago

Changelog

Source

17.0.0 (2023-11-08)

Blog post "Angular v17 is now available".

Breaking Changes

Node.js v16 support has been removed and the minimum support version has been bumped to 18.13.0.

Node.js v16 is planned to be End-of-Life on 2023-09-11. Angular will stop supporting Node.js v16 in Angular v17. For Node.js release schedule details, please see: https://github.com/nodejs/release#release-schedule

common

the NgSwitch directive now defaults to the === equality operator, migrating from the previously used == operator. NgSwitch expressions and / or individual condition values need adjusting to this stricter equality check. The added warning message should help pin-pointing NgSwitch usages where adjustments are needed.

core

Angular now requires zone.js version ~0.14.0
Versions of TypeScript older than 5.2 are no longer supported.
The mutate method was removed from the WritableSignal interface and completely dropped from the public API surface. As an alternative, please use the update method and make immutable changes to the object.

Example before:
```
items.mutate(itemsArray => itemsArray.push(newItem));
```
Example after:
```
items.update(itemsArray => [itemsArray, …newItem]);
```
OnPush components that are created dynamically now only have their host bindings refreshed and ngDoCheck run during change detection if they are dirty. Previously, a bug in the change detection would result in the OnPush configuration of dynamically created components to be ignored when executing host bindings and the ngDoCheck function. This is rarely encountered but can happen if code has a handle on the ComponentRef instance and updates values read in the OnPush component template without then calling either markForCheck or detectChanges on that component's ChangeDetectorRef.

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,
}]
```
The withNoDomReuse() function was removed from the public API. If you need to disable hydration, you can exclude the provideClientHydration() call from provider list in your application (which would disable hydration features for the entire application) or use ngSkipHydration attribute to disable hydration for particular components. See this guide for additional information: https://angular.io/guide/hydration#how-to-skip-hydration-for-particular-components.

router

Absolute redirects no longer prevent further redirects. Route configurations may need to be adjusted to prevent infinite redirects where additional redirects were previously ignored after an absolute redirect occurred.
Routes with loadComponent would incorrectly cause child routes to inherit their data by default. The default paramsInheritanceStrategy is emptyOnly. If parent data should be inherited in child routes, this should be manually set to always.
urlHandlingStrategy has been removed from the Router public API. This should instead be configured through the provideRouter or RouterModule.forRoot APIs.
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.
The setupTestingRouter function has been removed. Use RouterModule.forRoot or provideRouter to setup the Router for tests instead.
malformedUriErrorHandler is no longer available in the RouterModule.forRoot options. URL parsing errors should instead be handled in the UrlSerializer.parse method.

6.0.2

Diff

fisker

published 6.0.2 • 5 months ago

Changelog

Source

16.0.2 (2023-05-17)

core

| Commit | Type | Description | | -- | -- | -- | | c1016d4e57 | fix | add additional component metadata to component ID generation (#50340) | | cc41758b59 | fix | allow onDestroy unregistration while destroying (#50237) | | 7d679bdb59 | fix | allow passing value of any type to isSignal function (#50035) |

6.0.1

Diff

fisker

published 6.0.1 • 5 months ago

Changelog

Source

16.0.1 (2023-05-10)

core

| Commit | Type | Description | | -- | -- | -- | | 52c74d3b4a | fix | add additional component metadata to component ID generation (#50203) | | 048b6b1e0d | fix | bootstrapApplication call not rejected when error is thrown in importProvidersFrom module (#50120) | | d68796782f | fix | handle hydration of root components with injected ViewContainerRef (#50136) | | f751ce6445 | fix | handle projection of hydrated containters into components that skip hydration (#50199) | | 346ab73dd9 | fix | only try to retrieve transferred state on the browser (#50144) |

6.0.0

Diff

fisker

published 6.0.0 • 5 months ago

Changelog

Source

16.0.0 (2023-05-03)

Blog post "Angular v16 is now available".

Breaking Changes

Angular Compatibility Compiler (ngcc) has been removed and as a result Angular View Engine libraries will no longer work
Deprecated EventManager method addGlobalEventListener has been removed as it is not used by Ivy.

bazel

Several changes to the Angular Package Format (APF)
- Removal of FESM2015
- Replacing ES2020 with ES2022
- Replacing FESM2020 with FESM2022
Several changes to the Angular Package Format (APF)
- Removal of FESM2015
- Replacing ES2020 with ES2022
- Replacing FESM2020 with FESM2022

common

MockPlatformLocation is now provided by default in tests. Existing tests may have behaviors which rely on BrowserPlatformLocation instead. For example, direct access to the window.history in either the test or the component rather than going through the Angular APIs (Location.getState()). The quickest fix is to update the providers in the test suite to override the provider again TestBed.configureTestingModule({providers: [{provide: PlatformLocation, useClass: BrowserPlatformLocation}]}). The ideal fix would be to update the code to instead be compatible with MockPlatformLocation instead.
If the 'ngTemplateOutletContext' is different from the context, it will result in a compile-time error.

Before the change, the following template was compiling:

interface MyContext {
  $implicit: string;
}

@Component({
  standalone: true,
  imports: [NgTemplateOutlet],
  selector: 'person',
  template: `
    <ng-container
      *ngTemplateOutlet="
        myTemplateRef;
        context: { $implicit: 'test', xxx: 'xxx' }
      "></ng-container>
  `,
})
export class PersonComponent {
  myTemplateRef!: TemplateRef<MyContext>;
}

However, it does not compile now because the 'xxx' property does not exist in 'MyContext', resulting in the error: 'Type '{ $implicit: string; xxx: string; }' is not assignable to type 'MyContext'.'

The solution is either:

add the 'xxx' property to 'MyContext' with the correct type or
add '$any(...)' inside the template to make the error disappear. However, adding '$any(...)' does not correct the error but only preserves the previous behavior of the code.
Deprecated XhrFactory export from @angular/common/http has been removed. Use XhrFactory from @angular/common instead.

compiler

- TypeScript 4.8 is no longer supported.

core

QueryList.filter now supports type guard functions, which will result in type narrowing. Previously if you used type guard functions, it resulted in no changes to the return type. Now the type would be narrowed, which might require updates to the application code that relied on the old behavior.
zone.js versions 0.11.x and 0.12.x are not longer supported.
- entryComponents has been deleted from the @NgModule and @Component public APIs. Any usages can be removed since they weren't doing anyting.
- ANALYZE_FOR_ENTRY_COMPONENTS injection token has been deleted. Any references can be removed.
ComponentRef.setInput will only set the input on the component if it is different from the previous value (based on Object.is equality). If code relies on the input always being set, it should be updated to copy objects or wrap primitives in order to ensure the input value differs from the previous call to setInput.
RendererType2.styles no longer accepts a nested arrays.
The APP_ID token value is no longer randomly generated. If you are bootstrapping multiple application on the same page you will need to set to provide the APP_ID yourself.
```
bootstrapApplication(ComponentA, {
  providers: [
   { provide: APP_ID, useValue: 'app-a' },
   // ... other providers ...
  ]
});
```
The ReflectiveInjector and related symbols were removed. Please update the code to avoid references to the ReflectiveInjector symbol. Use Injector.create as a replacement to create an injector instead.
Node.js v14 support has been removed

Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.

platform-browser

The deprecated BrowserTransferStateModule was removed, since it's no longer needed. The TransferState class can be injected without providing the module. The BrowserTransferStateModule was empty starting from v14 and you can just remove the reference to that module from your applications.

platform-server

Users that are using SSR with JIT mode will now need to add import to @angular/compiler before bootstrapping the application.

NOTE: this does not effect users using the Angular CLI.

renderApplication method no longer accepts a root component as first argument. Instead, provide a bootstrapping function that returns a Promise<ApplicationRef>.

Before

const output: string = await renderApplication(RootComponent, options);

Now

const bootstrap = () => bootstrapApplication(RootComponent, appConfig);
const output: string = await renderApplication(bootstrap, options);

renderModuleFactory has been removed. Use renderModule instead.

router

The Scroll event's routerEvent property may also be a NavigationSkipped event. Previously, it was only a NavigationEnd event.
ComponentFactoryResolver has been removed from Router APIs. Component factories are not required to create an instance of a component dynamically. Passing a factory resolver via resolver argument is no longer needed and code can instead use ViewContainerRef.createComponent without the factory resolver.
The RouterEvent type is no longer present in the Event union type representing all router event types. If you have code using something like filter((e: Event): e is RouterEvent => e instanceof RouterEvent), you'll need to update it to filter((e: Event|RouterEvent): e is RouterEvent => e instanceof RouterEvent).
Tests which mock ActivatedRoute instances may need to be adjusted because Router.createUrlTree now does the right thing in more scenarios. This means that tests with invalid/incomplete ActivatedRoute mocks may behave differently than before. Additionally, tests may now navigate to a real URL where before they would navigate to the root. Ensure that tests provide expected routes to match. There is rarely production impact, but it has been found that relative navigations when using an ActivatedRoute that does not appear in the current router state were effectively ignored in the past. By creating the correct URLs, this sometimes resulted in different navigation behavior in the application. Most often, this happens when attempting to create a navigation that only updates query params using an empty command array, for example router.navigate([], {relativeTo: route, queryParams: newQueryParams}). In this case, the relativeTo property should be removed.

Deprecations

core

makeStateKey, StateKey and TransferState exports have been moved from @angular/platform-browser to @angular/core. Please update the imports.

- import {makeStateKey, StateKey, TransferState} from '@angular/platform-browser';
+ import {makeStateKey, StateKey, TransferState} from '@angular/core';

EnvironmentInjector.runInContext is now deprecated, with runInInjectionContext functioning as a direct replacement:

// Previous method version (deprecated):
envInjector.runInContext(fn);
// New standalone function:
runInInjectionContext(envInjector, fn);

The @Directive/@Component moduleId property is now deprecated. It did not have any effect for multiple major versions and will be removed in v17.

platform-browser

BrowserModule.withServerTransition has been deprecated. APP_ID should be used instead to set the application ID. NB: Unless, you render multiple Angular applications on the same page, setting an application ID is not necessary.

Before:
```
imports: [
  BrowserModule.withServerTransition({ appId: 'serverApp' }),
  ...
]
```
After:
```
imports: [
  BrowserModule,
  { provide: APP_ID, useValue: 'serverApp' },
  ...
],
```
ApplicationConfig has moved, please import ApplicationConfig from @angular/core instead.

platform-server

PlatformConfig.baseUrl and PlatformConfig.useAbsoluteUrl platform-server config options are deprecated as these were not used.

common

compiler

compiler-cli

core

forms

| Commit | Type | Description | | -- | -- | -- | | 07a1aa3004 | feat | Improve typings form (async)Validators (#48679) |

http

migrations

platform-browser

platform-server

router

| Commit | Type | Description | | -- | -- | -- | | ea32c3289a | feat | Expose information about the last successful Navigation (#49235) | | 455c728525 | feat | helper functions to convert class guards to functional (#48709) | | f982a3f965 | feat | Opt-in for binding Router information to component inputs (#49633) | | 1f055b90b6 | fix | Ensure anchor scrolling happens on ignored same URL navigations (#48025) | | 6193a3d406 | fix | fix = not parsed in router segment name (#47332) | | c0b1b7becf | fix | Remove deprecated ComponentFactoryResolver from APIs (#49239) | | 1e32709e0e | fix | remove RouterEvent from Event union type (#46061) | | 3c7e637374 | fix | Route matching should only happen once when navigating (#49163) | | 1600687fe5 | fix | Route matching should only happen once when navigating (#49163) | | 31f210bf2c | fix | Router.createUrlTree should work with any ActivatedRoute (#48508) |

service-worker

5.2.0

Diff

sosukesuzuki

published 5.2.0 • last year

Changelog

Source

15.2.0 (2023-02-22)

Deprecations

Class and InjectionToken guards and resolvers are deprecated. Instead, write guards as plain JavaScript functions and inject dependencies with inject from @angular/core.

common

compiler-cli

| Commit | Type | Description | | -- | -- | -- | | 0cf11167f1 | fix | incorrectly detecting forward refs when symbol already exists in file (#48988) |

core

language-service

migrations

| Commit | Type | Description | | -- | -- | -- | | 2796230e95 | fix | add enum in mode option in standalone schema (#48851) | | 816e76a578 | fix | automatically prune root module after bootstrap step (#49030) | | bdbf21d04b | fix | avoid generating imports with forward slashes (#48993) | | 32cf4e5cb9 | fix | avoid internal modules when generating imports (#48958) | | 521ccfbe6c | fix | avoid interrupting the migration if language service lookup fails (#49010) | | a40cd47aa7 | fix | avoid modifying testing modules without declarations (#48921) | | 1afa6ed322 | fix | don't add ModuleWithProviders to standalone test components (#48987) | | c98c6a8452 | fix | don't copy animations modules into the imports of test components (#49147) | | 8389557848 | fix | don't copy unmigrated declarations into imports array (#48882) | | f82bdc4b01 | fix | don't delete classes that may provide dependencies transitively (#48866) | | 759db12e0b | fix | duplicated comments on migrated classes (#48966) | | ba38178d19 | fix | generate forwardRef for same file imports (#48898) | | 03fcb36cfd | fix | migrate HttpClientModule to provideHttpClient() (#48949) | | 2de6dae16d | fix | migrate RouterModule.forRoot with a config object to use features (#48935) | | 770191cf1f | fix | migrate tests when switching to standalone bootstrap API (#48987) | | c7926b5773 | fix | move standalone migrations into imports (#48987) | | 65c74ed93e | fix | normalize paths to posix (#48850) | | 6377487b1a | fix | only exclude bootstrapped declarations from initial standalone migration (#48987) | | e9e4449a43 | fix | preserve tsconfig in standalone migration (#48987) | | ffad1b49d9 | fix | reduce number of files that need to be checked (#48987) | | ba7a757cc5 | fix | return correct alias when conflicting import exists (#49139) | | 49a7c9f94a | fix | standalone migration incorrectly throwing path error for multi app projects (#48958) | | 584976e6c8 | fix | support --defaults in standalone migration (#48921) | | 03f47ac901 | fix | use consistent quotes in generated imports (#48876) | | ebae506d89 | fix | use import remapper in root component (#49046) | | 40c976c909 | fix | use NgForOf instead of NgFor (#49022) | | 4ac25b2aff | perf | avoid re-traversing nodes when resolving bootstrap call dependencies (#49010) | | 26cb7ab2e6 | perf | speed up language service lookups (#49010) |

platform-browser

| Commit | Type | Description | | -- | -- | -- | | bf4ad38117 | fix | remove styles from DOM of destroyed components (#48298) |

platform-server

| Commit | Type | Description | | -- | -- | -- | | 25e220a23a | fix | avoid duplicate TransferState info after renderApplication call (#49094) |

router

Special Thanks

Alan Agius, Alex Castle, Alex Rickabaugh, Andrew Kushnir, Andrew Scott, Dylan Hunn, Ikko Eltociear Ashimine, Ilyass, Jessica Janiuk, Joey Perrott, John Manners, Kalbarczyk, Kristiyan Kostadinov, Matthieu Riegler, Paul Gschwendtner, Pawel Kozlowski, Virginia Dooley, Walid Bouguima, cexbrayat and mgechev

5.1.0

Diff

sosukesuzuki

published 5.1.0 • last year

Changelog

Source

15.1.0 (2023-01-10)

Deprecations

router

CanLoad guards in the Router are deprecated. Use CanMatch instead.
router writable properties

The following strategies are meant to be configured by registering the application strategy in DI via the providers in the root NgModule or bootstrapApplication:
- routeReuseStrategy
- titleStrategy
- urlHandlingStrategy
The following options are meant to be configured using the options available in RouterModule.forRoot or provideRouter.
- onSameUrlNavigation
- paramsInheritanceStrategy
- urlUpdateStrategy
- canceledNavigationResolution
The following options are available in RouterModule.forRoot but not available in provideRouter:
- malformedUriErrorHandler - This was found to not be used anywhere internally.
- errorHandler - Developers can instead subscribe to Router.events and filter for NavigationError.

common

| Commit | Type | Description | | -- | -- | -- | | fe50813664 | feat | Add BrowserPlatformLocation to the public API (#48488) | | 2f4f0638c7 | fix | Add data attribtue to NgOptimizedImage (#48497) |

compiler

compiler-cli

| Commit | Type | Description | | -- | -- | -- | | caedef0f5b | fix | update @babel/core dependency and lock version (#48634) |

core

forms

| Commit | Type | Description | | -- | -- | -- | | 8aa8b4b77c | fix | Form provider FormsModule.withConfig return a FormsModule (#48526) |

language-service

localize

| Commit | Type | Description | | -- | -- | -- | | a1a8e91eca | fix | add triple slash type reference on @angular/localize on `ng add (#48502) |

migrations

| Commit | Type | Description | | -- | -- | -- | | cc284afbbc | fix | combine newly-added imports in import manager (#48620) |

router

Special Thanks

Alan Agius, Alex Castle, Alex Rickabaugh, Andrew Kushnir, Andrew Scott, Bob Watson, Charles Lyding, Derek Cormier, Doug Parker, Dylan Hunn, George Kalpakas, Greg Magolan, Jessica Janiuk, JiaLiPassion, Joey Perrott, Kristiyan Kostadinov, Matthieu Riegler, Paul Gschwendtner, Pawel Kozlowski, Renan Ferro, Tim Gates, Vadim, Virginia Dooley, ced, mgechev, piyush132000, robertIsaac and sr5434

5.0.2

Diff

fisker

published 5.0.2 • last year

Changelog

Source

15.0.2 (2022-11-30)

compiler-cli

| Commit | Type | Description | | -- | -- | -- | | 86a21f5569 | fix | accept inheriting the constructor from a class in a library (#48156) |

Special Thanks

Alan Agius, Andrew Scott, Aristeidis Bampakos, Bob Watson, Derek Cormier, JoostK, Kristiyan Kostadinov, Matthieu Riegler, Paul Gschwendtner, Pawel Kozlowski, Rokas Brazdžionis, mgechev and piyush132000

2 3

angular-html-parser - npm Package Versions

8.0.1

.css-1z04cui{margin-bottom:var(--chakra-space-4);font-size:var(--chakra-fontSizes-md);}18.0.1 (2024-05-29)

compiler

compiler-cli

core

migrations

8.0.0

18.0.0 (2024-05-22)

Breaking Changes

animations

common

compiler

compiler-cli

core

http

platform-browser

platform-browser-dynamic

platform-server

router

Deprecations

common

core

http

animations

common

compiler

compiler-cli

core

forms

http

language-service

migrations

platform-browser

platform-browser-dynamic

platform-server

router

service-worker

7.0.1

17.0.1 (2023-11-08)

http

migrations

7.0.0

17.0.0 (2023-11-08)

Breaking Changes

common

core

platform-browser

router

6.0.2

16.0.2 (2023-05-17)

core

6.0.1

16.0.1 (2023-05-10)

core

6.0.0

16.0.0 (2023-05-03)

Breaking Changes

bazel

common

compiler

core

platform-browser

platform-server

router

Deprecations

core

platform-browser

platform-server

common

compiler

compiler-cli

core

forms

http

migrations

platform-browser

platform-server

router

service-worker

18.0.1 (2024-05-29)