@logixjs/core
    Preparing search index...

    Interface RuntimeOptions

    interface RuntimeOptions {
        concurrencyPolicy?: ConcurrencyPolicy;
        debug?: true | DebugLayerOptions;
        devtools?: true | DevtoolsRuntimeOptions;
        hostScheduler?: HostScheduler;
        label?: string;
        layer?: Layer<any, never, never>;
        middleware?: MiddlewareStack;
        onError?: (cause: Cause<unknown>) => Effect<void>;
        readQuery?: RuntimeReadQueryOptions;
        stateTransaction?: RuntimeStateTransactionOptions;
    }

    Hierarchy (View Summary)

    Index

    Properties

    concurrencyPolicy?: ConcurrencyPolicy

    Runtime-level concurrency control plane.

    Converges unbounded concurrency into bounded (default 16), with module/provider overrides.

    debug?: true | DebugLayerOptions

    Optional Debug console output configuration.

    • true: enable Debug.layer() (auto mode).
    • Debug.DebugLayerOptions: forwarded to Debug.layer(options).

    Advanced: for full control, omit this option and provide your own Debug layers via options.layer.

    devtools?: true | DevtoolsRuntimeOptions

    Enable Devtools (explicit override).

    • true: use default DevtoolsRuntimeOptions.
    • DevtoolsRuntimeOptions: customize hub buffer size, DebugObserver filters, etc.
    hostScheduler?: HostScheduler

    Optional HostScheduler override for this Runtime.

    Use it when you need deterministic host scheduling (tests) or a custom host integration.

    NOTE:

    • TickScheduler captures HostScheduler at Layer build-time (073); overriding HostScheduler via options.layer is not sufficient unless the dependent layer is built under that override.
    • This option avoids the pitfall by injecting HostScheduler into the runtime tick services build pipeline.
    label?: string

    Optional runtime label (e.g. AppDemoRuntime) for Debug / DevTools grouping.

    layer?: Layer<any, never, never>
    middleware?: MiddlewareStack
    onError?: (cause: Cause<unknown>) => Effect<void>

    ReadQuery governance (e.g. strict gate policies).

    Runtime-level StateTransaction defaults.

    When not provided, modules fall back to NODE_ENV-based defaults; modules may override via ModuleDef.implement({ stateTransaction }).