import type { BootstrapContext } from './bootstrap.js'; export interface BootModule { path: string; } /** * Everything the boot touches, so that a test can replace it. The real ones are * wired in `headlessBoot.ts`. */ export interface HeadlessBootDeps { /** Core modules, then enabled extensions. */ modules(): BootModule[]; loadBootstrapScript(module: BootModule, context: BootstrapContext): Promise; lockHooks(): void; lockRegistry(): void; lockAddressRegistry(): void; refreshSetting(): Promise; ensureRoutesLoaded(): void; } export interface HeadlessBootOptions { /** Passed to every module's bootstrap; `process` says which process this is. */ context: BootstrapContext; /** The modules to boot. Default: core modules, then enabled extensions. */ modules?: BootModule[]; /** Load the settings once, after the bootstraps. Default false. */ refreshSettings?: boolean; /** Fill the route registry, so `buildUrl` works. Default false. */ loadRoutes?: boolean; } /** * Boots a process that has no Express app (the event process, the cron * process, the import worker): runs the `bootstrap` of every module in order, * then locks the hook system, the registry and the address registry, exactly * as the event process has always done. Without it, what the bootstraps register (processors, * hooks, the address normalization seam) would be missing, and the process * would write data that the admin would refuse. * * The two options are off by default. The event process and the cron process * ask for the routes (they build URLs for emails and jobs) but not for an * extra settings load: the setting module's own bootstrap already warms the * cache in every process, and they refresh it before each batch or job. The * import worker turns both on. * * If a bootstrap throws, nothing is locked and the error reaches the caller. */ export declare function runHeadlessBoot(options: HeadlessBootOptions, deps: HeadlessBootDeps): Promise;