import type { RawNode } from '@variance-authority/core/format';
/**
 * A text run whose font stack starts at a generic family.
 *
 * `font-family: monospace` is not a choice of typeface, it is a question put to
 * the host, and the host answers with whatever it considers monospace --
 * Menlo on one machine, Courier on the next, and in Chromium not always the
 * same answer in two renderer processes on the same machine. The glyphs then
 * differ while the markup, the styles and the computed `font-family` are all
 * identical, so nothing in the comparison can name the cause: this is the only
 * place where it is still visible.
 *
 * Only a stack whose *first* entry is generic is reported. `Menlo, monospace`
 * names a face and falls back to the host; that is a declaration with a safety
 * net, and warning about it would make the diagnostic noise.
 *
 * And only where the choice was made: a rule matching this element, an inline
 * style, or an element the user agent renders monospace. A generic inherited
 * from a page-level reset reaches every text run in every subject of the suite,
 * and a diagnostic that fires on all of them is wallpaper -- the subject that
 * actually asked for a host typeface would be indistinguishable from the rest.
 */
export declare function hostChosenFonts(root: RawNode): {
    readonly family: string;
    readonly more: number;
} | undefined;
/**
 * `"Brand Sans", Inter, monospace` → `['brand sans', 'inter', 'monospace']`.
 *
 * Split on the commas outside quotes, unquoted, and lower-cased, because family
 * names match without regard to ASCII case.
 */
export declare function familiesIn(value: string): readonly string[];
//# sourceMappingURL=typeface.d.ts.map