/**
 * Shared client-side navigation intent helpers.
 *
 * Browser runtimes use the same low-level mechanics to:
 * - locate the anchor associated with a click, pointer, or hover event,
 * - persist the last valid pointer or hover target while a navigation is in flight,
 * - recover the final intended href when the DOM changes before the click lands.
 *
 * Keeping those mechanics here lets browser-router and react-router share one
 * implementation while preserving their router-specific interception rules.
 *
 * @module
 */
/**
 * Timestamped navigation intent captured from pointer or hover activity.
 */
export type EcoPendingNavigationIntent = {
    href: string;
    timestamp: number;
};
/**
 * Finds the nearest matching anchor within an event's composed path.
 *
 * This works across Shadow DOM boundaries, which is required for delegated
 * navigation handling when links are rendered inside custom elements.
 *
 * @param event - Pointer or mouse event being inspected.
 * @param linkSelector - Selector that identifies navigable anchors.
 * @returns The matched anchor element, or `null` when no matching anchor exists.
 */
export declare function getAnchorFromNavigationEvent(event: MouseEvent | PointerEvent, linkSelector: string): HTMLAnchorElement | null;
/**
 * Returns whether an href targets a static asset that should use a full document load.
 */
export declare function isStaticAssetHref(href: string): boolean;
/**
 * Resolves a previously captured intent while a navigation is still in flight.
 *
 * @remarks
 * Pending intents expire quickly because they bridge pointer or hover capture
 * and the later click when the DOM changes during a rapid navigation sequence.
 */
export declare function recoverPendingNavigationHref(intent: EcoPendingNavigationIntent | null, hasInFlightNavigation: boolean, now: number, maxAgeMs?: number): string | null;