import { type FrameworkSpec } from "./frameworks.js";
/**
 * Files identical in every site scaffold, taken from the base directory.
 *
 * Listed rather than globbed: a glob would silently absorb a file someone adds to the base for one
 * framework's benefit, which is the failure this is meant to end. Adding a shared file means saying so
 * here, and `site-composition.test.ts` fails if this list and the directory disagree.
 */
export declare const SHARED_SITE_FILES: readonly string[];
/** Files each framework supplies itself, relative to its overlay directory. */
export declare const FRAMEWORK_SITE_FILES: readonly string[];
/** Route files, whose extension is the framework's own. */
export declare const ROUTE_BASENAMES: readonly string[];
/** Extension the framework's route files carry. */
export declare function routeExtension(framework: FrameworkSpec): string;
/** The base directory: the shared files plus React's own, which is also the React overlay. */
export declare const SITE_BASE_DIR: string;
export declare function overlayDir(framework: FrameworkSpec): string;
/** Every file a site scaffold emits, and the text it holds. Generated files only. */
export declare function generatedSiteFiles(framework: FrameworkSpec): Map<string, string>;
export interface MaterializeOptions {
    /** Overwrite an existing destination. Default false, which refuses rather than clobbers. */
    readonly force?: boolean;
}
/**
 * Write a complete site scaffold into `target`.
 *
 * Refusing an occupied destination is the default and is preserved deliberately: `cp`'s
 * `errorOnExist` did that before this was generated, and losing it would turn a mistyped path into
 * silent data loss in someone's working directory. `--force` is what `bun create nifra .` needs.
 */
export declare function materializeSite(target: string, id: string, options?: MaterializeOptions): Promise<void>;
//# sourceMappingURL=site.d.ts.map