ai-functions/dist/sandbox.d.ts

Core AI primitives for building intelligent applications

/**
 * Sandbox execution boundary for ai-functions.
 *
 * ALL dynamic code execution in ai-functions is delegated to ai-evaluate's
 * V8-isolate sandbox (Cloudflare Dynamic Workers). `new Function`/`eval` are
 * banned in this package — they are broken under Workers and unsandboxed under
 * Node.
 *
 * ## The env boundary
 *
 * "Zero env plumbing" is NOT achievable:
 * - The Workers entry (`ai-evaluate`) requires a `LOADER` binding (and, for the
 *   test path, a `TEST` service binding) to be passed in `env`.
 * - That entry imports `cloudflare:workers`, which is Node-incompatible, so it
 *   cannot be imported eagerly in a Node/dev process.
 *
 * The clean boundary is therefore an **explicit, optional `env`**:
 * - When a host Workers `env` (carrying `LOADER` + `TEST`) is supplied, run on
 *   the real Dynamic Workers loader via `ai-evaluate`.
 * - When absent (Node / dev / tests), import from `ai-evaluate/node`, which
 *   falls back to Miniflare and runs with no live Worker.
 *
 * The `ai-evaluate/node` module is only imported when no `env` is present, so a
 * Node process never pulls in `cloudflare:workers`.
 */
import type { EvaluateOptions, EvaluateResult, SandboxEnv } from 'ai-evaluate';
export type { SandboxEnv } from 'ai-evaluate';
/**
 * Run an evaluation in the appropriate sandbox.
 *
 * @param options - What to evaluate (`script`, or `module` + `tests`, etc.)
 * @param env - Optional host Workers env carrying `LOADER` (+ `TEST` for the
 *   test path). When omitted, falls back to the Miniflare-backed Node entry.
 */
export declare function runInSandbox(options: EvaluateOptions, env?: SandboxEnv): Promise<EvaluateResult>;
//# sourceMappingURL=sandbox.d.ts.map