@angular/router 22.0.0-next.0 → 22.0.0-next.10

package/types/_router_module-chunk.d.ts

@@ -1,11 +1,11 @@
 /**
- * @license Angular v22.0.0-next.0
+ * @license Angular v22.0.0-next.10
  * (c) 2010-2026 Google LLC. https://angular.dev/
  * License: MIT
  */
 
 import * as i0 from '@angular/core';
-import { InjectionToken, Signal, EnvironmentInjector, ComponentRef, EventEmitter, OnDestroy, OnInit, SimpleChanges, ProviderToken, Type, NgModuleFactory, Provider, EnvironmentProviders, OnChanges, Renderer2, ElementRef, AfterContentInit, QueryList, ChangeDetectorRef, ModuleWithProviders } from '@angular/core';
+import { InjectionToken, EnvironmentInjector, ComponentRef, EventEmitter, Signal, OnDestroy, OnInit, SimpleChanges, Type, ProviderToken, NgModuleFactory, Provider, EnvironmentProviders, OnChanges, Renderer2, ElementRef, AfterContentInit, QueryList, ChangeDetectorRef, ModuleWithProviders } from '@angular/core';
 import { Observable } from 'rxjs';
 import { LocationStrategy } from '@angular/common';
 
@@ -695,6 +695,274 @@ declare function convertToParamMap(params: Params): ParamMap;
  */
 declare function defaultUrlMatcher(segments: UrlSegment[], segmentGroup: UrlSegmentGroup, route: Route): UrlMatchResult | null;
 
+/**
+ * Allowed values in an `ExtraOptions` object that configure
+ * when the router performs the initial navigation operation.
+ *
+ * * 'enabledNonBlocking' - (default) The initial navigation starts after the
+ * root component has been created. The bootstrap is not blocked on the completion of the initial
+ * navigation.
+ * * 'enabledBlocking' - The initial navigation starts before the root component is created.
+ * The bootstrap is blocked until the initial navigation is complete. This value should be set in
+ * case you use [server-side rendering](guide/ssr), but do not enable [hydration](guide/hydration)
+ * for your application.
+ * * 'disabled' - The initial navigation is not performed. The location listener is set up before
+ * the root component gets created. Use if there is a reason to have
+ * more control over when the router starts its initial navigation due to some complex
+ * initialization logic.
+ *
+ * @see {@link /api/router/RouterModule#forRoot forRoot}
+ *
+ * @publicApi
+ */
+type InitialNavigation = 'disabled' | 'enabledBlocking' | 'enabledNonBlocking';
+/**
+ * Extra configuration options that can be used with the `withRouterConfig` function.
+ *
+ * @see [Router configuration options](guide/routing/customizing-route-behavior#router-configuration-options)
+ *
+ * @publicApi
+ */
+interface RouterConfigOptions {
+    /**
+     * Configures how the Router attempts to restore state when a navigation is cancelled.
+     *
+     * 'replace' - Always uses `location.replaceState` to set the browser state to the state of the
+     * router before the navigation started. This means that if the URL of the browser is updated
+     * _before_ the navigation is canceled, the Router will simply replace the item in history rather
+     * than trying to restore to the previous location in the session history. This happens most
+     * frequently with `urlUpdateStrategy: 'eager'` and navigations with the browser back/forward
+     * buttons.
+     *
+     * 'computed' - Will attempt to return to the same index in the session history that corresponds
+     * to the Angular route when the navigation gets cancelled. For example, if the browser back
+     * button is clicked and the navigation is cancelled, the Router will trigger a forward navigation
+     * and vice versa.
+     *
+     * Note: the 'computed' option is incompatible with any `UrlHandlingStrategy` which only
+     * handles a portion of the URL because the history restoration navigates to the previous place in
+     * the browser history rather than simply resetting a portion of the URL.
+     *
+     * The default value is `replace` when not set.
+     *
+     * @see [Handle canceled navigations](guide/routing/customizing-route-behavior#handle-canceled-navigations)
+     *
+     */
+    canceledNavigationResolution?: 'replace' | 'computed';
+    /**
+     * Configures the default for handling a navigation request to the current URL.
+     *
+     * If unset, the `Router` will use `'ignore'`.
+     *
+     * @see {@link OnSameUrlNavigation}
+     *
+     * @see [React to same-URL navigations](guide/routing/customizing-route-behavior#react-to-same-url-navigations)
+     */
+    onSameUrlNavigation?: OnSameUrlNavigation;
+    /**
+     * Defines how the router merges parameters, data, and resolved data from parent to child
+     * routes.
+     *
+     * By default ('always'), a route inherits all parameters from its parent routes.
+     *
+     * Set to 'emptyOnly' to preserve the legacy behavior where a route only inherits the parent
+     * route's parameters when the route itself has an empty path or when the parent route doesn't
+     * have any component set.
+     *
+     * Note that when dealing with matrix parameters, "parent" refers to the parent `Route`
+     * config which does not necessarily mean the "URL segment to the left". When the `Route` `path`
+     * contains multiple segments, the matrix parameters must appear on the last segment. For example,
+     * matrix parameters for `{path: 'a/b', component: MyComp}` should appear as `a/b;foo=bar` and not
+     * `a;foo=bar/b`.
+     *
+     * @see [Control parameter inheritance](guide/routing/customizing-route-behavior#control-parameter-inheritance)
+     *
+     */
+    paramsInheritanceStrategy?: 'emptyOnly' | 'always';
+    /**
+     * Defines when the router updates the browser URL. By default ('deferred'),
+     * update after successful navigation.
+     * Set to 'eager' if prefer to update the URL at the beginning of navigation.
+     * Updating the URL early allows you to handle a failure of navigation by
+     * showing an error message with the URL that failed.
+     *
+     * @see [Decide when the URL updates](guide/routing/customizing-route-behavior#decide-when-the-url-updates)
+     *
+     */
+    urlUpdateStrategy?: 'deferred' | 'eager';
+    /**
+     * The default strategy to use for handling query params in `Router.createUrlTree` when one is not provided.
+     *
+     * The `createUrlTree` method is used internally by `Router.navigate` and `RouterLink`.
+     * Note that `QueryParamsHandling` does not apply to `Router.navigateByUrl`.
+     *
+     * When neither the default nor the queryParamsHandling option is specified in the call to `createUrlTree`,
+     * the current parameters will be replaced by new parameters.
+     *
+     * @see {@link Router#createUrlTree}
+     * @see {@link QueryParamsHandling}
+     *
+     * @see [Choose default query parameter handling](guide/routing/customizing-route-behavior#choose-default-query-parameter-handling)
+  
+     *
+     */
+    defaultQueryParamsHandling?: QueryParamsHandling;
+    /**
+     * When `true`, the `Promise` will instead resolve with `false`, as it does with other failed
+     * navigations (for example, when guards are rejected).
+  
+     * Otherwise the `Promise` returned by the Router's navigation with be rejected
+     * if an error occurs.
+     */
+    resolveNavigationPromiseOnError?: boolean;
+}
+/**
+ * Configuration options for the scrolling feature which can be used with `withInMemoryScrolling`
+ * function or `RouterModule.forRoot`.
+ *
+ * @publicApi
+ * @see withInMemoryScrolling
+ * @see RouterModule#forRoot
+ */
+interface InMemoryScrollingOptions {
+    /**
+     * When set to 'enabled', scrolls to the anchor element when the URL has a fragment.
+     * Anchor scrolling is disabled by default.
+     *
+     * Anchor scrolling does not happen on 'popstate'. Instead, we restore the position
+     * that we stored or scroll to the top.
+     */
+    anchorScrolling?: 'disabled' | 'enabled';
+    /**
+     * Configures if the scroll position needs to be restored when navigating back.
+     *
+     * * 'disabled'- (Default) Does nothing. Scroll position is maintained on navigation.
+     * * 'top'- Sets the scroll position to x = 0, y = 0 on all navigation.
+     * * 'enabled'- Restores the previous scroll position on backward navigation, else sets the
+     * position to the anchor if one is provided, or sets the scroll position to [0, 0] (forward
+     * navigation). This option will be the default in the future.
+     *
+     * You can implement custom scroll restoration behavior by adapting the enabled behavior as
+     * in the following example.
+     *
+     * ```ts
+     * class AppComponent {
+     *   movieData: any;
+     *
+     *   constructor(private router: Router, private viewportScroller: ViewportScroller,
+     * changeDetectorRef: ChangeDetectorRef) {
+     *   router.events.pipe(filter((event: Event): event is Scroll => event instanceof Scroll)
+     *     ).subscribe(e => {
+     *       fetch('http://example.com/movies.json').then(response => {
+     *         this.movieData = response.json();
+     *         // update the template with the data before restoring scroll
+     *         changeDetectorRef.detectChanges();
+     *
+     *         if (e.position) {
+     *           viewportScroller.scrollToPosition(e.position);
+     *         }
+     *       });
+     *     });
+     *   }
+     * }
+     * ```
+     */
+    scrollPositionRestoration?: 'disabled' | 'enabled' | 'top';
+}
+/**
+ * Configuration options for the component input binding feature which can be used
+ * with `withComponentInputBinding` function or `RouterModule.forRoot`
+ *
+ * @publicApi
+ * @see withComponentInputBinding
+ * @see RouterModule#forRoot
+ * @see [Disable query parameter binding](guide/routing/common-router-tasks#disable-query-parameter-binding)
+ */
+interface ComponentInputBindingOptions {
+    /**
+     * When true (default), will configure query parameters to bind to component
+     * inputs.
+     */
+    queryParams?: boolean;
+}
+/**
+ * A set of configuration options for a router module, provided in the
+ * `forRoot()` method.
+ *
+ * @see {@link /api/router/RouterModule#forRoot forRoot}
+ *
+ *
+ * @publicApi
+ */
+interface ExtraOptions extends InMemoryScrollingOptions, RouterConfigOptions {
+    /**
+     * When true, log all internal navigation events to the console.
+     * Use for debugging.
+     */
+    enableTracing?: boolean;
+    /**
+     * When true, enable the location strategy that uses the URL fragment
+     * instead of the history API.
+     */
+    useHash?: boolean;
+    /**
+     * One of `enabled`, `enabledBlocking`, `enabledNonBlocking` or `disabled`.
+     * When set to `enabled` or `enabledBlocking`, the initial navigation starts before the root
+     * component is created. The bootstrap is blocked until the initial navigation is complete. This
+     * value should be set in case you use [server-side rendering](guide/ssr), but do not enable
+     * [hydration](guide/hydration) for your application. When set to `enabledNonBlocking`,
+     * the initial navigation starts after the root component has been created.
+     * The bootstrap is not blocked on the completion of the initial navigation. When set to
+     * `disabled`, the initial navigation is not performed. The location listener is set up before the
+     * root component gets created. Use if there is a reason to have more control over when the router
+     * starts its initial navigation due to some complex initialization logic.
+     */
+    initialNavigation?: InitialNavigation;
+    /**
+     * When true, enables binding information from the `Router` state directly to the inputs of the
+     * component in `Route` configurations. Can also accept an `ComponentInputBindingOptions` object
+     * to set whether to exclude queryParams from binding.
+     */
+    bindToComponentInputs?: boolean | ComponentInputBindingOptions;
+    /**
+     * When true, enables view transitions in the Router by running the route activation and
+     * deactivation inside of `document.startViewTransition`.
+     *
+     * @see https://developer.chrome.com/docs/web-platform/view-transitions/
+     * @see https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API
+     * @experimental 17.0
+     */
+    enableViewTransitions?: boolean;
+    /**
+     * A custom error handler for failed navigations.
+     * If the handler returns a value, the navigation Promise is resolved with this value.
+     * If the handler throws an exception, the navigation Promise is rejected with the exception.
+     *
+     * @see RouterConfigOptions
+     */
+    errorHandler?: (error: any) => RedirectCommand | any;
+    /**
+     * Configures a preloading strategy.
+     * One of `PreloadAllModules` or `NoPreloading` (the default).
+     */
+    preloadingStrategy?: any;
+    /**
+     * Configures the scroll offset the router will use when scrolling to an element.
+     *
+     * When given a tuple with x and y position value,
+     * the router uses that offset each time it scrolls.
+     * When given a function, the router invokes the function every time
+     * it restores scroll position.
+     */
+    scrollOffset?: [number, number] | (() => [number, number]);
+}
+/**
+ * A DI token for the router service.
+ *
+ * @publicApi
+ */
+declare const ROUTER_CONFIGURATION: InjectionToken<ExtraOptions>;
+
 /**
  * An `InjectionToken` provided by the `RouterOutlet` and can be set using the `routerOutletData`
  * input.
@@ -1034,6 +1302,7 @@ type RestoredState = {
     [k: string]: any;
     navigationId: number;
     ɵrouterPageId?: number;
+    ɵrouterUrl?: string;
 };
 /**
  * Information about a navigation operation.
@@ -2425,7 +2694,8 @@ interface LoadedRouterConfig {
  *
  * @Injectable()
  * class CanActivateTeam implements CanActivate {
- *   constructor(private permissions: Permissions, private currentUser: UserToken) {}
+ *   private readonly permissions = inject(Permissions);
+ *   private readonly currentUser = inject(UserToken);
  *
  *   canActivate(
  *     route: ActivatedRouteSnapshot,
@@ -2538,7 +2808,8 @@ type CanActivateFn = (route: ActivatedRouteSnapshot, state: RouterStateSnapshot)
  *
  * @Injectable()
  * class CanActivateTeam implements CanActivateChild {
- *   constructor(private permissions: Permissions, private currentUser: UserToken) {}
+ *   private readonly permissions = inject(Permissions);
+ *   private readonly currentUser = inject(UserToken);
  *
  *   canActivateChild(
  *     route: ActivatedRouteSnapshot,
@@ -2621,7 +2892,8 @@ type CanActivateChildFn = (childRoute: ActivatedRouteSnapshot, state: RouterStat
  * ```ts
  * @Injectable()
  * class CanDeactivateTeam implements CanDeactivate<TeamComponent> {
- *   constructor(private permissions: Permissions, private currentUser: UserToken) {}
+ *   private readonly permissions = inject(Permissions);
+ *   private readonly currentUser = inject(UserToken);
  *
  *   canDeactivate(
  *     component: TeamComponent,
@@ -2692,9 +2964,14 @@ type CanDeactivateFn<T> = (component: T, currentRoute: ActivatedRouteSnapshot, c
  *
  * @Injectable()
  * class CanMatchTeamSection implements CanMatch {
- *   constructor(private permissions: Permissions, private currentUser: UserToken) {}
- *
- *   canMatch(route: Route, segments: UrlSegment[]): Observable<boolean>|Promise<boolean>|boolean {
+ *   private readonly permissions = inject(Permissions);
+ *   private readonly currentUser = inject(UserToken);
+ *
+ *   canMatch(
+ *     route: Route,
+ *     segments: UrlSegment[],
+ *     currentSnapshot: PartialMatchRouteSnapshot,
+ *   ): Observable<boolean> | Promise<boolean> | boolean {
  *     return this.permissions.canAccess(this.currentUser, route, segments);
  *   }
  * }
@@ -2732,7 +3009,7 @@ type CanDeactivateFn<T> = (component: T, currentRoute: ActivatedRouteSnapshot, c
  * @see [CanMatch](guide/routing/route-guards#canmatch)
  */
 interface CanMatch {
-    canMatch(route: Route, segments: UrlSegment[], currentSnapshot?: PartialMatchRouteSnapshot): MaybeAsync<GuardResult>;
+    canMatch(route: Route, segments: UrlSegment[], currentSnapshot: PartialMatchRouteSnapshot): MaybeAsync<GuardResult>;
 }
 /**
  * The signature of a function used as a `canMatch` guard on a `Route`.
@@ -2748,15 +3025,13 @@ interface CanMatch {
  *
  * @param route The route configuration.
  * @param segments The URL segments that have not been consumed by previous parent route evaluations.
- * @param currentSnapshot The current route snapshot up to this point in the matching process. While this parameter is optional,
- * it will always be defined when called by the Router. It is only optional for backwards compatibility with functions defined prior
- * to the introduction of this parameter.
+ * @param currentSnapshot The current route snapshot up to this point in the matching process.
  *
  * @publicApi
  * @see {@link Route}
  * @see [CanMatch](guide/routing/route-guards#canmatch)
  */
-type CanMatchFn = (route: Route, segments: UrlSegment[], currentSnapshot?: PartialMatchRouteSnapshot) => MaybeAsync<GuardResult>;
+type CanMatchFn = (route: Route, segments: UrlSegment[], currentSnapshot: PartialMatchRouteSnapshot) => MaybeAsync<GuardResult>;
 /**
  * A subset of the `ActivatedRouteSnapshot` interface that includes only the known data
  * up to the route matching phase. Some data are not accurately known
@@ -2784,7 +3059,7 @@ type PartialMatchRouteSnapshot = Pick<ActivatedRouteSnapshot, 'routeConfig' | 'u
  * ```ts
  * @Injectable({ providedIn: 'root' })
  * export class HeroResolver implements Resolve<Hero> {
- *   constructor(private service: HeroService) {}
+ *   private readonly service = inject(HeroService);
  *
  *   resolve(
  *     route: ActivatedRouteSnapshot,
@@ -2825,7 +3100,7 @@ type PartialMatchRouteSnapshot = Pick<ActivatedRouteSnapshot, 'routeConfig' | 'u
  * })
  * export class HeroComponent {
  *
- *  constructor(private activatedRoute: ActivatedRoute) {}
+ *   private readonly activatedRoute = inject(ActivatedRoute);
  *
  *  ngOnInit() {
  *    this.activatedRoute.data.subscribe(({ hero }) => {
@@ -2992,7 +3267,8 @@ type ResolveFn<T> = (route: ActivatedRouteSnapshot, state: RouterStateSnapshot)
  *
  * @Injectable()
  * class CanLoadTeamSection implements CanLoad {
- *   constructor(private permissions: Permissions, private currentUser: UserToken) {}
+ *   private readonly permissions = inject(Permissions);
+ *   private readonly currentUser = inject(UserToken);
  *
  *   canLoad(route: Route, segments: UrlSegment[]): Observable<boolean>|Promise<boolean>|boolean {
  *     return this.permissions.canLoadChildren(this.currentUser, route, segments);
@@ -3797,257 +4073,6 @@ declare class RouterLinkActive implements OnChanges, OnDestroy, AfterContentInit
     static ɵdir: i0.ɵɵDirectiveDeclaration<RouterLinkActive, "[routerLinkActive]", ["routerLinkActive"], { "routerLinkActiveOptions": { "alias": "routerLinkActiveOptions"; "required": false; }; "ariaCurrentWhenActive": { "alias": "ariaCurrentWhenActive"; "required": false; }; "routerLinkActive": { "alias": "routerLinkActive"; "required": false; }; }, { "isActiveChange": "isActiveChange"; }, ["links"], never, true, never>;
 }
 
-/**
- * Allowed values in an `ExtraOptions` object that configure
- * when the router performs the initial navigation operation.
- *
- * * 'enabledNonBlocking' - (default) The initial navigation starts after the
- * root component has been created. The bootstrap is not blocked on the completion of the initial
- * navigation.
- * * 'enabledBlocking' - The initial navigation starts before the root component is created.
- * The bootstrap is blocked until the initial navigation is complete. This value should be set in
- * case you use [server-side rendering](guide/ssr), but do not enable [hydration](guide/hydration)
- * for your application.
- * * 'disabled' - The initial navigation is not performed. The location listener is set up before
- * the root component gets created. Use if there is a reason to have
- * more control over when the router starts its initial navigation due to some complex
- * initialization logic.
- *
- * @see {@link /api/router/RouterModule#forRoot forRoot}
- *
- * @publicApi
- */
-type InitialNavigation = 'disabled' | 'enabledBlocking' | 'enabledNonBlocking';
-/**
- * Extra configuration options that can be used with the `withRouterConfig` function.
- *
- * @see [Router configuration options](guide/routing/customizing-route-behavior#router-configuration-options)
- *
- * @publicApi
- */
-interface RouterConfigOptions {
-    /**
-     * Configures how the Router attempts to restore state when a navigation is cancelled.
-     *
-     * 'replace' - Always uses `location.replaceState` to set the browser state to the state of the
-     * router before the navigation started. This means that if the URL of the browser is updated
-     * _before_ the navigation is canceled, the Router will simply replace the item in history rather
-     * than trying to restore to the previous location in the session history. This happens most
-     * frequently with `urlUpdateStrategy: 'eager'` and navigations with the browser back/forward
-     * buttons.
-     *
-     * 'computed' - Will attempt to return to the same index in the session history that corresponds
-     * to the Angular route when the navigation gets cancelled. For example, if the browser back
-     * button is clicked and the navigation is cancelled, the Router will trigger a forward navigation
-     * and vice versa.
-     *
-     * Note: the 'computed' option is incompatible with any `UrlHandlingStrategy` which only
-     * handles a portion of the URL because the history restoration navigates to the previous place in
-     * the browser history rather than simply resetting a portion of the URL.
-     *
-     * The default value is `replace` when not set.
-     *
-     * @see [Handle canceled navigations](guide/routing/customizing-route-behavior#handle-canceled-navigations)
-     *
-     */
-    canceledNavigationResolution?: 'replace' | 'computed';
-    /**
-     * Configures the default for handling a navigation request to the current URL.
-     *
-     * If unset, the `Router` will use `'ignore'`.
-     *
-     * @see {@link OnSameUrlNavigation}
-     *
-     * @see [React to same-URL navigations](guide/routing/customizing-route-behavior#react-to-same-url-navigations)
-     */
-    onSameUrlNavigation?: OnSameUrlNavigation;
-    /**
-     * Defines how the router merges parameters, data, and resolved data from parent to child
-     * routes.
-     *
-     * By default ('emptyOnly'), a route inherits the parent route's parameters when the route itself
-     * has an empty path (meaning its configured with path: '') or when the parent route doesn't have
-     * any component set.
-     *
-     * Set to 'always' to enable unconditional inheritance of parent parameters.
-     *
-     * Note that when dealing with matrix parameters, "parent" refers to the parent `Route`
-     * config which does not necessarily mean the "URL segment to the left". When the `Route` `path`
-     * contains multiple segments, the matrix parameters must appear on the last segment. For example,
-     * matrix parameters for `{path: 'a/b', component: MyComp}` should appear as `a/b;foo=bar` and not
-     * `a;foo=bar/b`.
-     *
-     * @see [Control parameter inheritance](guide/routing/customizing-route-behavior#control-parameter-inheritance)
-     *
-     */
-    paramsInheritanceStrategy?: 'emptyOnly' | 'always';
-    /**
-     * Defines when the router updates the browser URL. By default ('deferred'),
-     * update after successful navigation.
-     * Set to 'eager' if prefer to update the URL at the beginning of navigation.
-     * Updating the URL early allows you to handle a failure of navigation by
-     * showing an error message with the URL that failed.
-     *
-     * @see [Decide when the URL updates](guide/routing/customizing-route-behavior#decide-when-the-url-updates)
-     *
-     */
-    urlUpdateStrategy?: 'deferred' | 'eager';
-    /**
-     * The default strategy to use for handling query params in `Router.createUrlTree` when one is not provided.
-     *
-     * The `createUrlTree` method is used internally by `Router.navigate` and `RouterLink`.
-     * Note that `QueryParamsHandling` does not apply to `Router.navigateByUrl`.
-     *
-     * When neither the default nor the queryParamsHandling option is specified in the call to `createUrlTree`,
-     * the current parameters will be replaced by new parameters.
-     *
-     * @see {@link Router#createUrlTree}
-     * @see {@link QueryParamsHandling}
-     *
-     * @see [Choose default query parameter handling](guide/routing/customizing-route-behavior#choose-default-query-parameter-handling)
-  
-     *
-     */
-    defaultQueryParamsHandling?: QueryParamsHandling;
-    /**
-     * When `true`, the `Promise` will instead resolve with `false`, as it does with other failed
-     * navigations (for example, when guards are rejected).
-  
-     * Otherwise the `Promise` returned by the Router's navigation with be rejected
-     * if an error occurs.
-     */
-    resolveNavigationPromiseOnError?: boolean;
-}
-/**
- * Configuration options for the scrolling feature which can be used with `withInMemoryScrolling`
- * function or `RouterModule.forRoot`.
- *
- * @publicApi
- * @see withInMemoryScrolling
- * @see RouterModule#forRoot
- */
-interface InMemoryScrollingOptions {
-    /**
-     * When set to 'enabled', scrolls to the anchor element when the URL has a fragment.
-     * Anchor scrolling is disabled by default.
-     *
-     * Anchor scrolling does not happen on 'popstate'. Instead, we restore the position
-     * that we stored or scroll to the top.
-     */
-    anchorScrolling?: 'disabled' | 'enabled';
-    /**
-     * Configures if the scroll position needs to be restored when navigating back.
-     *
-     * * 'disabled'- (Default) Does nothing. Scroll position is maintained on navigation.
-     * * 'top'- Sets the scroll position to x = 0, y = 0 on all navigation.
-     * * 'enabled'- Restores the previous scroll position on backward navigation, else sets the
-     * position to the anchor if one is provided, or sets the scroll position to [0, 0] (forward
-     * navigation). This option will be the default in the future.
-     *
-     * You can implement custom scroll restoration behavior by adapting the enabled behavior as
-     * in the following example.
-     *
-     * ```ts
-     * class AppComponent {
-     *   movieData: any;
-     *
-     *   constructor(private router: Router, private viewportScroller: ViewportScroller,
-     * changeDetectorRef: ChangeDetectorRef) {
-     *   router.events.pipe(filter((event: Event): event is Scroll => event instanceof Scroll)
-     *     ).subscribe(e => {
-     *       fetch('http://example.com/movies.json').then(response => {
-     *         this.movieData = response.json();
-     *         // update the template with the data before restoring scroll
-     *         changeDetectorRef.detectChanges();
-     *
-     *         if (e.position) {
-     *           viewportScroller.scrollToPosition(e.position);
-     *         }
-     *       });
-     *     });
-     *   }
-     * }
-     * ```
-     */
-    scrollPositionRestoration?: 'disabled' | 'enabled' | 'top';
-}
-/**
- * A set of configuration options for a router module, provided in the
- * `forRoot()` method.
- *
- * @see {@link /api/router/routerModule#forRoot forRoot}
- *
- *
- * @publicApi
- */
-interface ExtraOptions extends InMemoryScrollingOptions, RouterConfigOptions {
-    /**
-     * When true, log all internal navigation events to the console.
-     * Use for debugging.
-     */
-    enableTracing?: boolean;
-    /**
-     * When true, enable the location strategy that uses the URL fragment
-     * instead of the history API.
-     */
-    useHash?: boolean;
-    /**
-     * One of `enabled`, `enabledBlocking`, `enabledNonBlocking` or `disabled`.
-     * When set to `enabled` or `enabledBlocking`, the initial navigation starts before the root
-     * component is created. The bootstrap is blocked until the initial navigation is complete. This
-     * value should be set in case you use [server-side rendering](guide/ssr), but do not enable
-     * [hydration](guide/hydration) for your application. When set to `enabledNonBlocking`,
-     * the initial navigation starts after the root component has been created.
-     * The bootstrap is not blocked on the completion of the initial navigation. When set to
-     * `disabled`, the initial navigation is not performed. The location listener is set up before the
-     * root component gets created. Use if there is a reason to have more control over when the router
-     * starts its initial navigation due to some complex initialization logic.
-     */
-    initialNavigation?: InitialNavigation;
-    /**
-     * When true, enables binding information from the `Router` state directly to the inputs of the
-     * component in `Route` configurations.
-     */
-    bindToComponentInputs?: boolean;
-    /**
-     * When true, enables view transitions in the Router by running the route activation and
-     * deactivation inside of `document.startViewTransition`.
-     *
-     * @see https://developer.chrome.com/docs/web-platform/view-transitions/
-     * @see https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API
-     * @experimental 17.0
-     */
-    enableViewTransitions?: boolean;
-    /**
-     * A custom error handler for failed navigations.
-     * If the handler returns a value, the navigation Promise is resolved with this value.
-     * If the handler throws an exception, the navigation Promise is rejected with the exception.
-     *
-     * @see RouterConfigOptions
-     */
-    errorHandler?: (error: any) => RedirectCommand | any;
-    /**
-     * Configures a preloading strategy.
-     * One of `PreloadAllModules` or `NoPreloading` (the default).
-     */
-    preloadingStrategy?: any;
-    /**
-     * Configures the scroll offset the router will use when scrolling to an element.
-     *
-     * When given a tuple with x and y position value,
-     * the router uses that offset each time it scrolls.
-     * When given a function, the router invokes the function every time
-     * it restores scroll position.
-     */
-    scrollOffset?: [number, number] | (() => [number, number]);
-}
-/**
- * A DI token for the router service.
- *
- * @publicApi
- */
-declare const ROUTER_CONFIGURATION: InjectionToken<ExtraOptions>;
-
 /**
  * This component is used internally within the router to be a placeholder when an empty
  * router-outlet is needed. For example, with a config such as:
@@ -4135,4 +4160,4 @@ declare class RouterModule {
 declare const ROUTER_INITIALIZER: InjectionToken<(compRef: ComponentRef<any>) => void>;
 
 export { ActivatedRoute, ActivatedRouteSnapshot, ActivationEnd, ActivationStart, BaseRouteReuseStrategy, ChildActivationEnd, ChildActivationStart, DefaultUrlSerializer, EventType, GuardsCheckEnd, GuardsCheckStart, NavigationCancel, NavigationCancellationCode, NavigationEnd, NavigationError, NavigationSkipped, NavigationSkippedCode, NavigationStart, PRIMARY_OUTLET, ROUTER_CONFIGURATION, ROUTER_INITIALIZER, ROUTER_OUTLET_DATA, ROUTER_PROVIDERS, RedirectCommand, ResolveEnd, ResolveStart, RouteConfigLoadEnd, RouteConfigLoadStart, RouteReuseStrategy, Router, RouterEvent, RouterLink, RouterLinkActive, RouterModule, RouterOutlet, RouterState, RouterStateSnapshot, RoutesRecognized, Scroll, UrlSegment, UrlSegmentGroup, UrlSerializer, UrlTree, convertToParamMap, defaultUrlMatcher, destroyDetachedRouteHandle, isActive, ɵEmptyOutletComponent };
-export type { CanActivate, CanActivateChild, CanActivateChildFn, CanActivateFn, CanDeactivate, CanDeactivateFn, CanLoad, CanLoadFn, CanMatch, CanMatchFn, Data, DefaultExport, DeprecatedGuard, DeprecatedResolve, DetachedRouteHandle, Event, ExtraOptions, GuardResult, InMemoryScrollingOptions, InitialNavigation, IsActiveMatchOptions, LoadChildren, LoadChildrenCallback, LoadedRouterConfig, MaybeAsync, Navigation, NavigationBehaviorOptions, NavigationExtras, OnSameUrlNavigation, ParamMap, Params, PartialMatchRouteSnapshot, QueryParamsHandling, RedirectFunction, Resolve, ResolveData, ResolveFn, RestoredState, Route, RouterConfigOptions, RouterOutletContract, Routes, RunGuardsAndResolvers, UrlCreationOptions, UrlMatchResult, UrlMatcher };
+export type { CanActivate, CanActivateChild, CanActivateChildFn, CanActivateFn, CanDeactivate, CanDeactivateFn, CanLoad, CanLoadFn, CanMatch, CanMatchFn, ComponentInputBindingOptions, Data, DefaultExport, DeprecatedGuard, DeprecatedResolve, DetachedRouteHandle, Event, ExtraOptions, GuardResult, InMemoryScrollingOptions, InitialNavigation, IsActiveMatchOptions, LoadChildren, LoadChildrenCallback, LoadedRouterConfig, MaybeAsync, Navigation, NavigationBehaviorOptions, NavigationExtras, OnSameUrlNavigation, ParamMap, Params, PartialMatchRouteSnapshot, QueryParamsHandling, RedirectFunction, Resolve, ResolveData, ResolveFn, RestoredState, Route, RouterConfigOptions, RouterOutletContract, Routes, RunGuardsAndResolvers, UrlCreationOptions, UrlMatchResult, UrlMatcher };