DEFAULT_EVAL_CAP_IN_MILLISECONDS
The default per-eval cap, in milliseconds: the budget one evalInObsidian closure has to fit inside.
Everything awaited inside a single closure shares this one budget — every lib.waitUntil timeout and every settle sleep — so a closure’s declared waits have to sum to less than this, not merely be individually shorter.
An overrun is reported as EvalCapExceededError, which names the cap, the transport that enforced it, and the option that sets it. Raising that option is almost never the right answer: a closure that needs to wait longer than this should not be waiting inside Obsidian at all. pollInObsidian is the sanctioned shape — short closures, with the waiting done from Node — and it exists precisely so no single eval is ever long.
Both transports default to this value: it is what ObsidianCdpTransportOptions.commandTimeoutInMilliseconds and ObsidianAndroidAppiumTransportOptions.scriptTimeoutInMilliseconds fall back to when they are omitted.
Import:
import { DEFAULT_EVAL_CAP_IN_MILLISECONDS } from 'obsidian-integration-testing';Signature:
const DEFAULT_EVAL_CAP_IN_MILLISECONDS: 30000Type: 30000