/**
 * Public element shape — kept structural so consumers don't infer through
 * either framework's internal VNode type. Matches the shape `Island`
 * returns from `@takazudo/zfb`.
 */
export type ViewTransitionsElement = {
    readonly type: string;
    readonly props: Readonly<Record<string, unknown>>;
    readonly key: unknown;
};
/**
 * `<ViewTransitions />` — DEPRECATED: this component is now a typed
 * no-op. Cross-document View Transitions are opted in via the
 * `@view-transition { navigation: auto; }` CSS at-rule, NOT via this
 * component. Add the at-rule to your top-level stylesheet (outside
 * any `@layer` block — see https://developer.mozilla.org/en-US/docs/Web/CSS/@view-transition).
 *
 * The export is kept so consumers' existing `<ViewTransitions />`
 * mounts compile unchanged.
 *
 * The previous implementation injected an inline router IIFE that
 * called `event.preventDefault()` and `document.startViewTransition`
 * around `window.location.href = url`. That pattern is INCOMPATIBLE
 * with cross-document VT: Chromium treats the script reload as
 * excluded from `auto`, so no `::view-transition-*` pseudo-elements
 * ever materialize. See
 * https://developer.chrome.com/docs/web-platform/view-transitions/cross-document.
 *
 * @deprecated The runtime injection is removed. Use the
 * `@view-transition` CSS at-rule on both source and destination
 * documents.
 */
export declare function ViewTransitions(): readonly ViewTransitionsElement[];