Function isSandboxRuntimeAborted

@ifc-lite/sandbox — QuickJS-in-WASM sandboxed script execution

Runs user scripts in a secure, isolated environment with only the bim.* API exposed. No DOM, no global fetch. Outbound HTTP is available only through bim.network.fetch, gated by the network permission (off by default) plus an exact-host grant list re-checked on every call — see network-request.ts and bridge-network.ts.

Example

import { createSandbox } from '@ifc-lite/sandbox';
import { createBimContext } from '@ifc-lite/sdk';

const bim = createBimContext({ backend: myBackend });
const sandbox = await createSandbox(bim, {
  permissions: { mutate: true },
  limits: { timeoutMs: 10_000 },
});

const result = await sandbox.eval(`
  const walls = bim.query.byType('IfcWall');
  console.log('Found', walls.length, 'walls');
  walls.length;
`);

console.log(result.value);  // number of walls
console.log(result.logs);   // captured console.log output

sandbox.dispose();

isSandboxRuntimeAborted(): boolean

Whether a QuickJS teardown has ever aborted a WASM module in this process (#1922).

Latched and never cleared — it is a diagnostic, not a health check. It does not mean scripting is broken: the poisoned module is retired at the moment of the abort and the next sandbox gets a fresh one, so a true here is compatible with a fully working sandbox. A host wanting to know whether a particular sandbox is still trustworthy should read Sandbox.moduleRetired instead; this is for telemetry and for explaining a script that crashed.

Returns boolean

Function isSandboxRuntimeAborted

Example

Returns boolean

Settings