//#region src/builders/web/bundle.d.ts
export interface BundleCockpitWebOptions {
  hostRoot: string;
  /** Package roots to scan for doompiWeb manifests, usually the installed composition. */
  pluginRoots: readonly string[];
  /** Output directory; receives web/, plugins/, generated/, and pluginRoots.json. */
  outDir: string;
  onNotice?: (message: string) => void;
}
export interface BundleCockpitWebResult {
  /** Full synchronized SPA retained for CLI compatibility. */
  assetsDir: string;
  /** Standalone session plugin composition artifacts. */
  pluginsDir: string;
  pluginIds: string[];
}
/**
 * Builds the cockpit SPA against the installed plugin set.
 *
 * This is what `doompi sync` calls: manifests come from the given package
 * roots (no hardcoded plugin dependencies anywhere), the generated entry
 * modules are aliased over the committed builtin registry, and Vite compiles
 * the host shell and each plugin's shipped web source into one browser bundle.
 * The roots file beside
 * the bundle lets the dev server serve the same composition with hot reload.
 */
export declare function bundleCockpitWeb(options: BundleCockpitWebOptions): Promise<BundleCockpitWebResult>;
//#endregion
//# sourceMappingURL=bundle.d.mts.map