import type { Key, ReactNode } from "react";
/**
 * One rung of the trail.
 *
 * Which of the three it becomes is read off the fields it carries, so
 * a caller mapping a path to items never has to say what the rung
 * *is* — only where it goes:
 *
 *  - `href` — a real `<a href>`, through `TextLink`, so an in-app path
 *    goes through the injected router exactly as every other link in
 *    the library does.
 *  - `onSelect` and no `href` — a `<button>` painted as the same link.
 *    For a trail over state that has no URL: image-viewer's folder
 *    path and mux-magic's file-explorer modal both move a browser
 *    around a disk without touching the address bar.
 *  - neither — plain text. On the **last** item that is the current
 *    page, and it carries `aria-current="page"`.
 */
export type BreadcrumbItem = {
    href?: string;
    /**
     * React's list key. Optional, because `label` is a node and cannot
     * be one; the fallback is `href`, then the position. Pass it when
     * two rungs can share an `href` or the trail reorders.
     */
    key?: Key;
    label: ReactNode;
    /**
     * Runs on activation. With an `href` it runs alongside the
     * navigation (closing a drawer, say); without one it IS the
     * navigation.
     */
    onSelect?: () => void;
};
export type BreadcrumbsProps = {
    className?: string;
    items: readonly BreadcrumbItem[];
    /**
     * The `<nav>` landmark's name. Two trails on one page need two
     * different names, or axe's `landmark-unique` fails.
     */
    label?: string;
    /**
     * Drawn between rungs, always `aria-hidden`. The default is a
     * chevron drawn in CSS borders rather than a `›` character: the
     * library ships no symbol glyphs in a default, because a font that
     * lacks one paints nothing
     * (`docs/decisions/2026-07-29-ship-no-icons-and-no-symbol-glyphs.md`).
     * Folio's `/` is a fine override — it is the app's choice to make.
     */
    separator?: ReactNode;
};
/**
 * A path back up a hierarchy: `Places › Office › Office Shelves`.
 *
 * Folio, image-viewer and mux-magic each hand-rolled one, and they
 * disagreed on everything a shared shape should settle — one was a
 * `<nav>` of bare links with no list, two were `<div>`s of buttons
 * with no landmark, one truncated the current segment, one gave the
 * current folder no `aria-current`. This is the WAI-ARIA APG
 * breadcrumb pattern: a `<nav>` landmark around an `<ol>`, because
 * the order is the meaning.
 *
 * The current page is the **last item with nowhere to go**. A trail
 * that sits above a heading already naming the page — Whereabouts'
 * `Places › Office` over an `Office Shelves` heading — gives every
 * item an `href`, and then no rung is current, which is correct: the
 * page is named once, by the heading.
 */
export declare const Breadcrumbs: ({ className, items, label, separator, }: BreadcrumbsProps) => ReactNode;
//# sourceMappingURL=Breadcrumbs.d.ts.map