/**
 * Subset of Next.js config shape used by withRevealUI.
 * Defined locally to avoid requiring `next` as a dependency of @revealui/core.
 * Consumers pass their full NextConfig through; we only access these fields.
 */
interface NextConfig {
    env?: Record<string, string | undefined>;
    webpack?: (config: Record<string, unknown>, context: {
        isServer: boolean;
        dev: boolean;
        dir: string;
        [key: string]: unknown;
    }) => Record<string, unknown>;
    turbopack?: {
        resolveAlias?: Record<string, string>;
    };
    headers?: () => Promise<Array<{
        source: string;
        headers: Array<{
            key: string;
            value: string;
        }>;
    }>>;
    images?: {
        remotePatterns?: Array<Record<string, unknown>>;
    };
    [key: string]: unknown;
}
export interface WithRevealUIOptions {
    /** Path to the RevealUI config file (relative to Next.js project root) */
    configPath?: string;
    /** Whether to enable admin UI */
    admin?: boolean;
    /** Admin route path */
    adminRoute?: string;
    /** API route path */
    apiRoute?: string;
}
/**
 * Next.js configuration wrapper for RevealUI
 * Provides webpack aliases, environment variables, and build configuration
 *
 * MUST NOT alias the `@revealui/config` package specifier: that is a real
 * workspace package (type-safe env config). Aliasing it to the app's
 * revealui.config.ts shadows the package in every server bundle, so
 * `config.reveal` / `config.database` reads resolve against the CMS instance
 * config and come back undefined at runtime (prod admin passkey/MFA 500s,
 * 2026-06-10). Apps load their CMS config via relative imports or their own
 * `@reveal-config` alias instead.
 */
export declare function withRevealUI(nextConfig?: NextConfig, options?: WithRevealUIOptions): NextConfig;
export {};
//# sourceMappingURL=withRevealUI.d.ts.map