import { ConfigModel, ObservableContainer } from '@rxdi/core'; import { Observable } from 'rxjs'; export declare function isLambdaRuntime(): boolean; /** * Synchronous check: did a user bundle already deliver its AppModule via * the bridge? Useful right after `await import(userBundle)` to decide * between the new (Bootstrap-based) and legacy (default-export-function) * specialize paths without paying a Promise-race timeout. */ export declare function isLambdaModuleDelivered(): boolean; /** * Called by the host (e.g. FissionPlugin) before loading the user bundle. * Returns a Promise that resolves with the user's AppModule once the * lambda-aware Bootstrap intercepts it. */ export declare function awaitLambdaModule(): Promise; /** * Called by the lambda-aware Bootstrap wrapper to hand the user's AppModule * to the waiting host. If the host hasn't called `awaitLambdaModule()` yet, * we cache the module so the next caller gets it. */ export declare function deliverLambdaModule(appModule: Function): void; /** * Resets bridge state. Useful for tests and (eventually) re-specialization * if a single container ever needs to load more than one user bundle. */ export declare function resetLambdaBridge(): void; /** * Drop-in replacement for `@rxdi/core` Bootstrap that detects Lambforge mode * via env. In lambda mode, the AppModule is delivered to the bridge and a * dummy observable resolves so user code's `.subscribe(...)` still fires * (which lets `console.log('Server started')` style callbacks run as the * user expects). In normal mode, this is exactly the upstream Bootstrap. */ export declare function Bootstrap(app: Function, config?: ConfigModel): Observable;