import { Theme } from '../utils';
/**
 * Blocking script for the document <head>. On a first visit from a browser
 * that doesn't send Sec-CH-Prefers-Color-Scheme (Safari, Firefox), it seeds
 * the `theme` cookie from the OS preference and, when dark, hides the body
 * behind a `#__theme-init` style so the light server render never flashes,
 * and rewrites `<meta name="theme-color">` to `darkThemeColor` so the browser
 * chrome (Safari tab bar, Android toolbar) doesn't hold the light tint until
 * hydration — the server had no cookie to resolve, and the provider's own
 * meta sync runs too late by definition. The meta rewrite mirrors
 * ClientThemeProvider's sync (single canonical tag, media-scoped ones
 * removed), which takes over from here after hydration.
 * ClientThemeProvider removes the `#__theme-init` style once the corrected
 * theme has committed on the client. Pass your dark theme's page background
 * so the brief pre-hydration frame matches it; pass `darkThemeColor` when
 * your provider uses a non-default `$themeColor` (e.g. "primary") so the
 * pre-hydration tint matches that token's dark value instead.
 */
export declare function createThemeInitScript(darkBackground?: string, darkThemeColor?: string): string;
/** createThemeInitScript() with the default dark background and theme-color (#000). */
export declare const themeInitScript: string;
/**
 * Resolves a `theme` cookie value ("light" | "dark") to a theme object.
 * Meant for server code: read the cookie, resolve, pass the result to
 * ClientThemeProvider via $initial (or use it for viewport theme-color).
 */
export declare function resolveTheme(cookieValue: string | undefined, theme: Theme, themeDark?: Theme): Theme;