strongbus - v3.1.0
    Preparing search index...

    Interface Options

    interface Options {
        name?: string;
        thresholds?: Partial<ListenerThresholds>;
        logger?: LoggerProvider;
        verbose?: boolean;
        coalesceDownstreamLifecycleEvents?: boolean;
        duplicateSubscriptionStrategy?: Partial<DuplicateSubscriptionStrategy>;
        onUnhandledEvent?:
            | "throw"
            | "ignore"
            | ((event: string | number | symbol, payload: unknown) => void);
        onUseAfterDestroy?: false | "error" | "info" | "debug" | "warn" | "throw";
    }
    Index
    name? thresholds? logger? verbose? coalesceDownstreamLifecycleEvents? duplicateSubscriptionStrategy? onUnhandledEvent? onUseAfterDestroy?
    name?: string

    "Anonymous" - A name for the bus. Included in warn/info/error potential memory leak messages and unhandled event errors thrown

    thresholds?: Partial<ListenerThresholds>

    ListenerThresholds

    logger?: LoggerProvider

    () => Logger - How to log potential memory leaks, if thresholds are < Infinity. When omitted, a built-in console adapter is used.

    verbose?: boolean

    [false] - should memory leak warnings be output on every listener added above the thresholds, or only at intervals

    coalesceDownstreamLifecycleEvents?: boolean

    [true] - when true, coalesce will/did add/remove hooks to one emission per event key during pipe() / unpipe() reconcile of a heavily-subscribed downstream bus

    duplicateSubscriptionStrategy?: Partial<DuplicateSubscriptionStrategy>

    how duplicate listenable+handler registrations behave

    onUnhandledEvent?:
        | "throw"
        | "ignore"
        | ((event: string | number | symbol, payload: unknown) => void)

    ['ignore'] — what to do when an event is emitted with no listeners: 'ignore' (default no-op), 'throw', or a custom (event, payload) => void callback

    onUseAfterDestroy?: false | "error" | "info" | "debug" | "warn" | "throw"

    [false] - what to do when a monitoring or subscription method is called after destroy(): false runs it as usual; a LogLevel logs StrongbusLogCode.UseAfterDestroy, then skips it and returns an inert stub; 'throw' throws instead. When set to any of these, emit and destroy become silent no-ops. Introspection is never affected. Calls made while destroy() is still running are skipped and logged at debug under every setting, including false.

    Settings
    Member Visibility

    On This Page
    Properties