import { ReactNode } from 'react';
export type ThemedRootProps = {
    className?: string;
    /** True when this space is embedded in an application with a theme of its own — see `ThemeProvider`'s `scope`. */
    scoped?: boolean;
    children?: ReactNode;
};
/**
 * The SDK's own root, wearing the theme when the document is not this space's to write on.
 *
 * An embedded space cannot stamp `<html>` — the desktop window's chrome reads that class, and repainting the
 * application around a space is not what toggling the space's theme means. So the class lands here instead, on the
 * element the space actually occupies, which is all its own styles ever needed: `.dark` and `.light` declare
 * `color-scheme` wherever they sit, and Tailwind's `dark:` variant matches any ancestor.
 *
 * `system` writes nothing, here as everywhere else: with no class the space inherits whatever the host document
 * settled on, which for an embedded surface is the right default.
 *
 * It also says when the page is interactive: `data-hydrated` appears once React has taken over the server's markup
 * (at once for a page rendered in the browser). A space's CSS keys decorative motion that repaints every frame off it
 * — `[data-hydrated] .glow { animation-play-state: running; }` — so the load has the main thread to itself. And it
 * plays the arrivals that wait to be seen (`MotionReveal`).
 */
declare const ThemedRoot: ({ className, scoped, children }: ThemedRootProps) => import('react').JSX.Element;
export default ThemedRoot;