import type { MurasakiConfig } from '../config.js';
/**
 * Bundles every `'use server'` module under `srcDir` into a single Node ESM
 * "registry" (`dist/server/actions.mjs`), and every `src/api/**\/route.ts`
 * into a parallel routes registry (`dist/server/routes.mjs`), that
 * `assets/prod-server.mjs` loads at runtime to run actions/routes in
 * production — the prod counterpart of the dev middlewares'
 * `server.ssrLoadModule(id)` in vite-plugin/server-actions.ts and
 * vite-plugin/api-routes.ts.
 *
 * Both are found with a directory scan (like vite-plugin/routing.ts's route
 * scan) rather than by tracking what the client build's transform touches —
 * a scan doesn't depend on whether the client bundle's module graph happens
 * to reach a given file, so it can't miss one that got tree-shaken out of the
 * client chunk.
 */
export default function buildServer(cwd: string, srcDir: string, config: MurasakiConfig): Promise<void>;
/**
 * Remove only the framework-owned directive after the scanner has classified
 * the module. Replacing it with spaces preserves line/column positions for
 * diagnostics and sourcemaps while preventing Rollup from treating it as an
 * unsupported module-level runtime directive.
 */
export declare function stripLeadingMainDirective(code: string): string;
//# sourceMappingURL=build-server.d.ts.map