/**
 * False for the server render and the hydration render, true from the first commit
 * onward.
 *
 * A fact only the client knows (the window's width, a value in browser storage) cannot
 * be read during hydration. On the server it is simply absent, so the markup is built
 * without it; on the client it is right there, so the same component would render
 * something else and React would report a hydration mismatch it does not patch up: it
 * throws the server tree away and rebuilds the subtree. Deferring the read by one
 * render keeps the hydration pass byte-identical to the server and lets the real value
 * land in the commit immediately after, which is the same contract `ThemeProvider`'s
 * `ssrScheme` gives the colour axis.
 */
export declare function useHydrated(): boolean;
//# sourceMappingURL=use-hydrated.d.ts.map