OptionalallowWhether code runs on the page's main thread, NOT isolated, when the iframe can't start.
Defaults to false: the code-running tools then return an error to the model, and a
call 30 seconds or more later tries the iframe again. When true, the failure is final
and later runs stay on the main thread. MapAgentInstance.getCodeExecutionMode reports which happened.
OptionalloadOptional override of the worker's library source. By default, the SDK loads its own
inlined turf/h3 UMD and worker utilities (a separate lazy chunk), so this is rarely needed.
Supply it only to pin a specific build. The returned source replaces the bundled one whole:
return UMD/IIFE JavaScript (string or Promise of one) that defines self.turf and self.h3,
plus self.routeUtils and self.cluster if generated code uses them.
OptionaltimeoutWall-clock budget per isolated (browser) run, in ms. Defaults to 10000.
Tunes the sandbox execution of
analyseDatasets,deriveDatasets,createTrackerandclusterIncidentscode. The environment decides where the code runs. In the browser, it is a sandboxed, opaque-origin iframe + Web Worker (no DOM/storage access, no network via CSP, terminable on timeout). In Node / SSR, where that boundary has no equivalent, it is the main thread. The options below only apply in the browser.