papi-dts
    Preparing search index...

    Variable onDidLoseConnectionConst Experimental

    onDidLoseConnection: PlatformEvent<void>

    Fires when this process's own connection to the network is lost unexpectedly — the websocket closed without the app having asked it to.

    This is platform-internal core plumbing between the process that holds a client connection and the services that react to losing one, not part of the @papi/* surface — the same status as onDidDisconnectClient above, which is this seam in the opposite direction.

    This is a local, in-process event. Only a process that holds a client connection can lose one, so it fires exclusively on clients; in the process that owns the websocket server it is a real event that simply never fires. A deliberate disconnect does not fire it: intent travels in the close code, and a close the app asked for is not a loss. Neither does a connection that never opened — only an established connection can be lost, so a failed startup attempt is silent here.

    Relayed through this service's own emitter so subscribers can subscribe before there is an RPC handler to subscribe to. Carries no payload; the close detail is logged where it is observed.