/**
 * The function `getColorScheme` retrieves the content of the meta tag with the name "color-scheme"
 * from the document.
 * @returns The `getColorScheme` function returns the content attribute value of the meta tag with the
 * name "color-scheme" from the document.
 */
export declare function getColorScheme(): string | null | undefined;
/**
 * The function `getPreferredColorScheme` determines the preferred color scheme (dark or light) based
 * on the user's system settings.
 * @returns The `getPreferredColorScheme` function returns either 'dark' if the user prefers a dark
 * color scheme, 'light' if the user prefers a light color scheme, or 'light' if the browser does not
 * support `window.matchMedia`.
 */
export declare function getPreferredColorScheme(): "dark" | "light";
/**
 * Resolve a design-token CSS custom property to a concrete color for the active
 * color scheme.
 *
 * Resolution order is intentionally charts-safe:
 * 1. Return already-resolved concrete colors as-is (do not string-split them).
 * 2. For literal `light-dark(...)`, pick the scheme channel with a paren-aware
 *    parser and preserve hex when present (so `color + '80'` keeps working).
 * 3. Resolve nested `var(--token)` channels.
 * 4. Probe via computed `color` only when a authored hex/channel is unavailable.
 *
 * Missing tokens return `''` (with a console warning) to preserve existing
 * falsy fallbacks such as `getTokenThemeVal(token) || hex`.
 *
 * @param token - CSS custom property name, e.g. `--kd-color-background-ui`.
 * @returns A concrete color string (preferably `#RRGGBB` when authored that way),
 * or `''` when unresolved.
 *
 * Ensure `<meta name="color-scheme" content="light dark">` (or `light` / `dark`)
 * is present when tokens use `light-dark()`.
 */
export declare function getTokenThemeVal(token: string): string;
//# sourceMappingURL=color.d.ts.map