@spatius/avatarkit 1.3.1-beta.3 → 1.3.1-beta.5

package/dist/internal-telemetry.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Internal telemetry surface for the companion RTC SDK.
+ *
+ * `@spatius/avatarkit-rtc` reports into the same OpenObserve backend and shares
+ * this SDK's OTel providers, so its spans must sit on the same calibrated
+ * timeline. Without that, a client whose wall clock is off puts RTC spans at a
+ * time that does not line up with the server-side records they need to be read
+ * against.
+ *
+ * Deliberately NOT re-exported from the package root: this is a bridge between
+ * two first-party packages, not API for integrators. It exposes conversion only
+ * — nothing here can alter the clock baseline.
+ *
+ * NOTE: nothing in this file may be tagged `@internal`. The dts plugin runs with
+ * `stripInternal: true`, which erases such declarations from the emitted `.d.ts`
+ * — the entry would still export both functions at runtime while shipping an
+ * empty `export {}` type file, leaving the RTC package with no types.
+ *
+ * @packageDocumentation
+ */
+/**
+ * Convert a `performance.now()` reading taken earlier into a timeline
+ * timestamp (epoch ms), preferring the server-calibrated baseline and falling
+ * back to the local clock until calibration completes.
+ *
+ * Collect marks on the monotonic clock and convert at report time: the wall
+ * clock and `performance.now()` drift apart while the main thread is blocked,
+ * and calibration may not have finished when the mark was taken.
+ *
+ * @param mono - the `performance.now()` value recorded at collection time
+ */
+export declare function resolveMonoTimestamp(mono: number): number;
+/**
+ * Whether clock calibration against the backend has completed. Timestamps
+ * resolve either way; this only reports whether they are server-aligned yet.
+ */
+export declare function isClockCalibrated(): boolean;

package/dist/internal-telemetry.js

@@ -0,0 +1,45 @@
+import { h as clockSync } from "./logger-C61wOfFi.js";
+//#region internal-telemetry.ts
+/**
+* Internal telemetry surface for the companion RTC SDK.
+*
+* `@spatius/avatarkit-rtc` reports into the same OpenObserve backend and shares
+* this SDK's OTel providers, so its spans must sit on the same calibrated
+* timeline. Without that, a client whose wall clock is off puts RTC spans at a
+* time that does not line up with the server-side records they need to be read
+* against.
+*
+* Deliberately NOT re-exported from the package root: this is a bridge between
+* two first-party packages, not API for integrators. It exposes conversion only
+* — nothing here can alter the clock baseline.
+*
+* NOTE: nothing in this file may be tagged `@internal`. The dts plugin runs with
+* `stripInternal: true`, which erases such declarations from the emitted `.d.ts`
+* — the entry would still export both functions at runtime while shipping an
+* empty `export {}` type file, leaving the RTC package with no types.
+*
+* @packageDocumentation
+*/
+/**
+* Convert a `performance.now()` reading taken earlier into a timeline
+* timestamp (epoch ms), preferring the server-calibrated baseline and falling
+* back to the local clock until calibration completes.
+*
+* Collect marks on the monotonic clock and convert at report time: the wall
+* clock and `performance.now()` drift apart while the main thread is blocked,
+* and calibration may not have finished when the mark was taken.
+*
+* @param mono - the `performance.now()` value recorded at collection time
+*/
+function resolveMonoTimestamp(mono) {
+	return clockSync.resolveMono(mono);
+}
+/**
+* Whether clock calibration against the backend has completed. Timestamps
+* resolve either way; this only reports whether they are server-aligned yet.
+*/
+function isClockCalibrated() {
+	return clockSync.isReady();
+}
+//#endregion
+export { isClockCalibrated, resolveMonoTimestamp };