Interface: BootOptions

Properties

PropertyModifierTypeDescription
backend?readonlyRuntimeBackendKindRuntime backend selection. - browser runs inside browser workers and is the default. - server starts a managed server runtime immediately. - auto starts in the browser and promotes to the server backend for commands that require it, such as uv, native tools, or unsupported Python package stacks.
brokerUrl?readonlystring | URLRuntime broker base URL for server-backed sessions. Hosted projects normally receive this from the runtime boot service.
limits?readonlyPartial<RuntimeLimits>-
nativeInstallMode?readonlyNativeInstallMode-
nativePackagePolicy?readonly"error" | "replace"-
nativePackageReplacements?readonlyReadonly<Record<string, NativePackageReplacement>>-
onDiagnostic?readonly(event) => void-
packageRegistryUrl?readonlystring-
persistenceHandoff?readonly"wait" | "fail-fast"-
persistenceKey?readonlystring-
persistOnTeardown?readonlyboolean-
previewOriginTemplate?readonlystringIsolated preview origin template. Hosted projects normally receive https://{previewSessionId}.preview.verklet.com from the runtime boot service. Custom templates must contain {previewSessionId} and resolve to an HTTP(S) origin.
projectIdreadonlystringPublic project ID from a Verklet account. Create an account, select or create an organization, then copy the generated prj_... ID from /account. Unknown project IDs are rejected by the hosted boot service.
python?readonlyPythonRuntimeOptionsBrowser Python configuration. The default keeps backend: 'auto' browser-first: supported Python runs in Pyodide and unsupported workloads promote to the server backend when fallback is enabled.
requireWasm?readonlyboolean-
runtimeConfigUrl?readonlystring | false | URL-
runtimeId?readonlystring-
server?readonlyServerBackendOptionsServer-backend options used when backend is server or auto.
serviceWorker?readonlyfalse | PreviewServiceWorkerOptions-
wasmExecutionPolicy?readonlyWasmExecutionPolicy-