import React from 'react';
interface NavItemOwnProps {
    /** Figma's `Icon` slot — an optional leading icon. */
    icon?: React.ReactNode;
    /** Figma's `Show Chevron`. Set on a nav item that opens a menu, not a plain link. */
    showChevron?: boolean;
    /**
     * The page the user is on. Marks the item `aria-current="page"` and draws
     * the same indicator Tabs' underline does — so a section switcher built from
     * NavItems says where you are, in words for a screen reader and in more than
     * colour for everyone else.
     */
    isCurrent?: boolean;
    isDisabled?: boolean;
    /**
     * @deprecated Use `isDisabled`. Accepted as an alias for one minor version.
     */
    disabled?: boolean;
    children?: React.ReactNode;
    className?: string;
}
export type NavItemProps = NavItemOwnProps & (({
    href: string;
} & Omit<React.AnchorHTMLAttributes<HTMLAnchorElement>, keyof NavItemOwnProps>) | ({
    href?: undefined;
} & Omit<React.ButtonHTMLAttributes<HTMLButtonElement>, keyof NavItemOwnProps | 'type'>));
/**
 * Nav Item renders an `<a>` when given `href`, a `<button>` otherwise —
 * chosen by what the caller is actually building, the same judgment call
 * Menu and Select make. A primary nav bar is links; a nav item with
 * `showChevron` that opens a menu (no `href` of its own) is a button.
 *
 * Interaction state comes from React Aria rather than CSS pseudo-classes,
 * matching Button: `useHover` is pointer-aware so a tap does not stay
 * "hovered" until the next tap elsewhere, and `useFocusRing` shows the ring
 * only for keyboard navigation. The CSS keeps its own `:hover` /
 * `:focus-visible` rules so the stylesheet still works without React.
 */
export declare const NavItem: React.ForwardRefExoticComponent<NavItemProps & React.RefAttributes<HTMLButtonElement | HTMLAnchorElement>>;
export {};
//# sourceMappingURL=NavItem.d.ts.map