/**
 * Load `isolated-vm` for the Node line this worker runs on.
 *
 * The native addon is ABI-bound per Node major, so two builds ship as
 * optionalDependencies: `isolated-vm@6` for Node 22–24 and the aliased
 * `isolated-vm-next` (= `isolated-vm@7`) for Node 26+. Node 25 is an EOL
 * non-LTS line upstream skipped, and Bun cannot dlopen a V8 addon at all.
 * Both return `null` so the caller fails closed: the executor selector fails
 * an `isolate` run instead of forking a child for it. Mirrors
 * `packages/server/src/sandbox/run-script.ts`; the gateway adopting this
 * module is a follow-up.
 */
import type { IsolatedVm } from './ivm-types.js';
/**
 * Why this host cannot run an isolate, or `null` when the Node line has a
 * build. A load failure on an eligible line (native build skipped on this
 * platform) is reported by `loadIsolatedVm()` returning null; this only
 * classifies the runtime.
 */
export declare function isolatedVmUnavailableReason(): string | null;
/**
 * The optionalDependency that carries this Node line's isolated-vm build, or
 * `null` when the runtime has none (`isolatedVmUnavailableReason()` says why).
 * Shared by the loader and the self-check so both name the same package.
 */
export declare function isolatedVmSpecifier(): string | null;
/**
 * Resolve the isolated-vm module for this Node line, or `null` when it cannot
 * load. Memoized per process: the addon is loaded once and shared by every
 * isolate the worker creates.
 */
export declare function loadIsolatedVm(): Promise<IsolatedVm | null>;
//# sourceMappingURL=load.d.ts.map