import type { ReactNode } from "react";
import type { TabLinkItem, TabsOrientation } from "./tabItems.ts";
export type TabLinkProps = {
    isCurrent: boolean;
    item: TabLinkItem;
    orientation: TabsOrientation;
};
/**
 * One routed tab — and it is a real `<a href>`, through the same
 * `RouterLinkProvider` seam `NavLink` uses.
 *
 * ### It carries no `role="tab"`, and that is the whole point
 *
 * `role="tab"` on an anchor **overrides** the link role. A screen
 * reader then announces "tab", the reader expects a panel to appear
 * beside it, and instead the address changes and the page under it
 * is replaced. The APG tab pattern describes a disclosure inside one
 * document; it does not describe navigation, and `aria-controls`
 * has nothing to point at here because the section's content comes
 * from the router — an `<Outlet />` the app renders somewhere this
 * component cannot see.
 *
 * So a routed bar is what it actually is: a list of links inside a
 * named `<nav>`, with `aria-current="page"` on the one you are on.
 * That is `Nav`'s answer, and reusing it rather than restating it is
 * why `resolveActiveKey` decides the current item.
 *
 * What the tab pattern was *really* supplying here was the paint,
 * and the paint is shared through `toTabTriggerClass` — so this
 * looks identical to the `<button>` beside it in Storybook and is
 * announced correctly.
 */
export declare const TabLink: ({ isCurrent, item, orientation, }: TabLinkProps) => ReactNode;
//# sourceMappingURL=TabLink.d.ts.map