Documentation / @super-line/core / ClientTapRecord

Interface: ClientTapRecord

Defined in: packages/core/src/client-tap.ts:91

Cross-cutting metadata wrapping one ClientTapEvent — the counterpart of the server's InspectorEnvelope. The event stays a pure "what happened"; the envelope carries when, which client, and where in the stream.

seq is assigned by the CONSUMER, not the client, because it must be monotonic across every client on the page — and a page runs several (a session replacement deliberately runs the incumbent and its candidate at the same time). It is what lets a consumer reading through two channels at once dedup and detect gaps.

Properties

clientId

clientId: string

Defined in: packages/core/src/client-tap.ts:99

Which client on the page emitted it.

---

event

event: ClientTapEvent

Defined in: packages/core/src/client-tap.ts:93

The observation, with payloads snapshotted by the consumer.

---

seq

seq: number

Defined in: packages/core/src/client-tap.ts:95

Monotonic across all clients on the page; assigned at buffer time.

---

ts

ts: number

Defined in: packages/core/src/client-tap.ts:97

Emit time (epoch ms).