import type { ClarityConfig } from './types';
export declare const defaultConfig: ClarityConfig;
// `config` is exported synchronously, populated from `defaultConfig` and
// **mutated in place** when the user's `clarity.config.ts` (if any) finishes
// loading via `configReady`.
//
// Why not the obvious `export const config = await loadConfig()`: top-level
// await turns this module — and therefore *every* dependent of
// `@stacksjs/clarity` — into an async-init module. Anything bundled along
// with clarity inherits the TLA, so a single misbehaving config file (or a
// transient `bunfig` hang) can freeze importers like `@stacksjs/bunpress`
// at module-evaluation time. Keeping the export synchronous decouples
// "logger usable" from "user config resolved".
export declare const config: ClarityConfig;
/**
 * Resolves once the user's `clarity.config.{ts,js,json}` (if present) has
 * been merged onto `config`. Callers that need the resolved values can
 * `await configReady`; everyone else (the common case) just uses `config`
 * with default values until the project's overrides land.
 */
export declare const configReady: Promise<ClarityConfig>;