import * as class_variance_authority_types from 'class-variance-authority/types';
import { VariantProps } from 'class-variance-authority';
import React__default from 'react';

/**
 * Surface colours the main navigation can be themed with — exactly the
 * Footer's thirteen-name vocabulary, so a service that themes its footer
 * `primary-800` writes the same word here. Each name is the LIGHT-mode
 * surface; dark mode deepens it onto the same family's dark steps (see the
 * `color` variants below), so `color` expresses tonal weight rather than a
 * literal colour.
 *
 * The bar's text/background pairs are identical to the Footer's, so its
 * contrast conclusions carry over verbatim: every light pair clears WCAG 2.2
 * AA (1.4.3, 4.5:1) for the bar's text and 11 of the 13 also clear AAA
 * (1.4.6, 7:1). The two AA-only pairs are `primary-600` (4.57:1) and
 * `accent-600` (5.18:1), both with white ink; prefer the `-800` steps when a
 * service is held to AAA. In dark mode all thirteen clear AAA (worst 13.6:1).
 *
 * The mega panels always render on the house popup surface (`bg-popover`),
 * matching the nswds-app source where every dropdown was white regardless of
 * bar colour — only the panel's accent ink follows the colour family.
 */
declare const mainNavColors: readonly ["primary-800", "primary-600", "primary-400", "primary-200", "grey-800", "grey-600", "grey-400", "grey-200", "accent-800", "accent-600", "accent-400", "accent-200", "white"];
type MainNavColor = (typeof mainNavColors)[number];
declare const mainNavVariants: (props?: ({
    color?: "white" | "primary-800" | "primary-600" | "primary-400" | "primary-200" | "grey-800" | "grey-600" | "grey-400" | "grey-200" | "accent-800" | "accent-600" | "accent-400" | "accent-200" | null | undefined;
    border?: "none" | "both" | "top" | "bottom" | null | undefined;
} & class_variance_authority_types.ClassProp) | undefined) => string;
declare const mainNavContainerVariants: (props?: ({
    container?: "fluid" | "contained" | null | undefined;
} & class_variance_authority_types.ClassProp) | undefined) => string;
/**
 * Mega-panel accent ink, keyed by the same thirteen colour names as the bar.
 * The panel itself is always the house popup surface (`bg-popover`, white in
 * light mode) — parity with the app source, whose dropdown was white for
 * every variant — so the family only tints the featured lead link, hover ink
 * and cell borders. Declared on the Content element (not inherited from the
 * bar) because Base UI portals the panel to `document.body`: a custom
 * property set on the `<nav>` can never reach it.
 *
 * Light inks are the family's -800 step on white — grey-800 on white is
 * 15.1:1 and white on primary-800 is 14.4:1 (both AAA; contrast is symmetric,
 * ratios from header.tsx); accent-800 on white clears AAA per the Footer's
 * verified pairs. Dark inks step to the family's -200 — the same dark-mode
 * interactive ink link.tsx and navigation-menu.tsx already use on this
 * popover surface. The featured lead is text-xl bold, so even the softest
 * pair is far above the large-text AA floor (1.4.3, 3:1).
 */
declare const mainNavPanelVariants: (props?: ({
    color?: "white" | "primary-800" | "primary-600" | "primary-400" | "primary-200" | "grey-800" | "grey-600" | "grey-400" | "grey-200" | "accent-800" | "accent-600" | "accent-400" | "accent-200" | null | undefined;
} & class_variance_authority_types.ClassProp) | undefined) => string;
/** One link inside a mega panel. */
type MainNavLinkItem = {
    /** Visible link text, e.g. "Find support near you". */
    title: string;
    href: string;
};
/**
 * One top-level navigation item. With `links` it renders as a trigger opening
 * a mega panel (with `href` becoming the panel's featured lead link; without
 * an `href` the lead is a plain heading row — dev builds warn); without
 * `links` it renders as a plain link styled like the triggers. Recursion is
 * deliberately one level deep — mega panels list flat links, per the app
 * source's NavigationSection shape.
 */
type MainNavItem = {
    title: string;
    href?: string;
    links?: MainNavLinkItem[];
};
type MainNavProps = Omit<React__default.ComponentPropsWithoutRef<'nav'>, 'children'> & VariantProps<typeof mainNavVariants> & VariantProps<typeof mainNavContainerVariants> & {
    /** Top-level items; items with `links` open mega panels. */
    navigation: MainNavItem[];
    /**
     * The current page's href. The exact matching link gets
     * `aria-current="page"`, and the top-level item it belongs to (a plain
     * link, or the trigger whose panel contains it) gets the current-item
     * underline. The app source read this from next/navigation's
     * `usePathname` — a framework API this package must not import; compare
     * in the consumer and pass the result down.
     */
    currentHref?: string;
    /**
     * Stick to the top of the viewport as the page scrolls. Defaults to
     * `false`. When the nav renders below a sticky `Header`, set
     * `--main-nav-top` to the header's height so the two stack instead of
     * overlapping — this custom property replaces the app source's
     * `useSelectorHeight` DOM-measuring hook (the app measured `#nsw-header`
     * on every resize; a consumer that needs a live value can still measure
     * its own header and write the property, see the Sticky story).
     */
    sticky?: boolean;
    /** Drop shadow under the bar. Defaults to `true`. */
    shadow?: boolean;
    /** Classes applied to the inner width-constraining wrapper. */
    containerClassName?: string;
    /**
     * Shown in the bar when `navigation` is empty. Defaults to
     * "No navigation items available."; pass `null` to render an empty bar.
     *
     * An empty `navigation` array is a legitimate runtime state, not a data
     * mistake — a CMS with nothing published, a menu filtered down to nothing
     * by the reader's permissions, or a failed nav fetch all produce it. The
     * bar keeps its themed surface either way, so with no message it reads as
     * an unexplained coloured strip.
     */
    emptyMessage?: React__default.ReactNode;
    ref?: React__default.Ref<HTMLElement>;
};
/**
 * Full-width NSW site navigation bar with mega-menu panels — the data-driven
 * consolidation of the nswds-app `NavigationMenuMainNavigation` /
 * `MainNavigation` components, rebuilt on this package's `NavigationMenu`
 * (Base UI underneath).
 *
 * - `navigation` drives everything: items with `links` render a trigger whose
 *   mega panel shows a featured lead link (the section `href`; with no `href`
 *   the lead demotes to a plain heading row — dev builds warn) above a
 *   responsive 1/2/3-column grid of bordered section links; items without
 *   `links` render plain links styled like the triggers. All anchors render
 *   through `Link`, so a framework link injected via `LinkProvider`
 *   (e.g. next/link) is used automatically.
 * - `color` themes the bar with the Footer's thirteen-name vocabulary and its
 *   exact dark-mode deepening; every derived colour (halos, borders, focus
 *   outlines) resolves from a single `--main-nav-ink` per variant. Contrast
 *   conclusions are the Footer's, verbatim (see `mainNavColors`).
 * - Panels span the nav container's full width: a ResizeObserver on the inner
 *   container feeds each panel's inline width, and an `alignOffset` function
 *   shifts Base UI's trigger-anchored positioner back to the container's left
 *   edge (measured at position time from the open trigger, so it is exact for
 *   every trigger — this replaces the app source's panelMetrics state).
 *   The offset is physical and correct in BOTH directions: Base UI passes
 *   `align` to floating-ui as a physical placement and only mirrors a logical
 *   `side`, so nothing about this anchoring flips under RTL. See the comment
 *   on `alignOffset`, and the RightToLeft story that pins it.
 * - `container`, `border`, `shadow`, `sticky` mirror the house chrome
 *   components; the app's deprecated `showTopBorder`/`showBottomBorder` and
 *   `responsive` props are not ported (use `border` and
 *   `className="hidden lg:block"`).
 *
 * Accessibility: the outer `<nav>` is the landmark (default label "Main
 * navigation"; Base UI's own root is demoted to a `<div>` via `render` so the
 * page doesn't gain a nested nav landmark). Everything interactive is
 * inherited from Base UI via the sibling: triggers are real buttons with
 * `aria-expanded`/`aria-controls`, ArrowDown/Enter opens, arrow keys rove,
 * Escape and focus-out close, and the current page announces
 * `aria-current="page"` (WCAG 2.4.8). Focus indicators are 2px ink-derived
 * outlines that contrast on all thirteen surfaces and on the panel surface
 * (2.4.7, 2.4.13). The 220ms `closeDelay` reproduces the app's hover-out
 * grace timer through Base UI instead of a hand-rolled setTimeout.
 *
 * The default `id="nsw-main-navigation"` is kept for compatibility with
 * existing shells that target it (override via the `id` prop).
 */
declare function MainNav({ className, containerClassName, color, container, border, navigation, currentHref, sticky, shadow, emptyMessage, 'aria-label': ariaLabel, ref, ...props }: MainNavProps): React__default.JSX.Element;

export { MainNav, type MainNavColor, type MainNavItem, type MainNavLinkItem, type MainNavProps, mainNavColors, mainNavContainerVariants, mainNavPanelVariants, mainNavVariants };