/**
 * CSS string serialization.
 *
 * A Look string value reaches CSS as a CSS string, and JSON is not that
 * serialization. The two agree on `"` and `\` and on nothing else: JSON writes
 * a newline as `\n` and a tab as `\t`, while CSS reads `\` followed by a
 * non-hex-digit as that literal character, so `\n` renders the letter `n` and
 * the line break is silently lost. CSS spells a code point as `\` plus its hex
 * digits, terminated by one space. D51 rule 112.3 already recorded that the
 * JSON string rule was insufficient and that explicit target-aware escaping is
 * the fix; this is that escaping for the CSS target.
 *
 * Both the compile-time lowering and the emitted runtime need the same
 * serialization, so the two spellings are published together: `cssString` here
 * for the compiler, and `runtime/css-string.js` — read back as
 * `CSS_STRING_RUNTIME_BODY` — for the runtime body the emitter ships and every
 * `velar/look` module carries.
 */
/**
 * `value` as a complete double-quoted CSS string, quotes included, so this is
 * a drop-in replacement for `JSON.stringify` wherever a CSS string was meant.
 * Only `"`, `\`, the C0 controls, and U+007F need escaping; every other code
 * point, `•` and an emoji alike, is literal text in a UTF-8 stylesheet.
 */
export declare function cssString(value: string): string;
//# sourceMappingURL=css-string.d.ts.map