@oddin-gg/havik-player 2.9.3 → 2.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.cts CHANGED
@@ -660,11 +660,19 @@ export declare function licenseRequestHeaders(descriptor: StreamDescriptor, cred
660
660
  * the `/v1/playback` outcome ladder so a pushed event and a follow-up
661
661
  * `/v1/playback` call always agree:
662
662
  * live ↔ 200 OK (a serveable session exists — play now)
663
- * upcoming ↔ 425 Too Early (scheduled, not serving yet)
663
+ * upcoming ↔ 425 Too Early (scheduled, not serving yet; `liveStartsAt` says when)
664
+ * pending ↔ 425 Too Early (kickoff has passed, the stream is being packaged —
665
+ * no `liveStartsAt`; `live` follows within seconds
666
+ * to minutes)
664
667
  * ended ↔ 503 (was live; media stopped, still in catchup)
665
668
  * gone ↔ 410 Gone (ended past the catchup window)
669
+ *
670
+ * `pending` and `upcoming` ask the same thing of a player — wait — and the
671
+ * managed player treats them alike ("Starting soon…"). A host that renders
672
+ * its own waiting UI can tell them apart: `upcoming` has a kickoff to count
673
+ * down to, `pending` means the match is on and media is seconds away.
666
674
  */
667
- export declare type LiveState = 'live' | 'upcoming' | 'ended' | 'gone';
675
+ export declare type LiveState = 'live' | 'upcoming' | 'pending' | 'ended' | 'gone';
668
676
 
669
677
  export declare interface LiveStateEvent {
670
678
  matchUrn: string;
@@ -680,7 +688,13 @@ export declare interface LiveStateSubscription {
680
688
  close(): void;
681
689
  }
682
690
 
683
- export declare type MatchLiveStatus = 'upcoming' | 'live' | 'ended';
691
+ /**
692
+ * `pending` is the catalog's "kickoff has passed, the stream is being
693
+ * packaged" — not playable yet, `live` expected within seconds to minutes. It
694
+ * is NOT `upcoming` (which has a kickoff ahead) and not `live` (nothing serves
695
+ * yet); `/v1/playback` answers `425` for it without a `liveStartsAt`.
696
+ */
697
+ export declare type MatchLiveStatus = 'upcoming' | 'pending' | 'live' | 'ended';
684
698
 
685
699
  export declare interface MatchStatus {
686
700
  matchUrn: string;
package/dist/index.d.ts CHANGED
@@ -660,11 +660,19 @@ export declare function licenseRequestHeaders(descriptor: StreamDescriptor, cred
660
660
  * the `/v1/playback` outcome ladder so a pushed event and a follow-up
661
661
  * `/v1/playback` call always agree:
662
662
  * live ↔ 200 OK (a serveable session exists — play now)
663
- * upcoming ↔ 425 Too Early (scheduled, not serving yet)
663
+ * upcoming ↔ 425 Too Early (scheduled, not serving yet; `liveStartsAt` says when)
664
+ * pending ↔ 425 Too Early (kickoff has passed, the stream is being packaged —
665
+ * no `liveStartsAt`; `live` follows within seconds
666
+ * to minutes)
664
667
  * ended ↔ 503 (was live; media stopped, still in catchup)
665
668
  * gone ↔ 410 Gone (ended past the catchup window)
669
+ *
670
+ * `pending` and `upcoming` ask the same thing of a player — wait — and the
671
+ * managed player treats them alike ("Starting soon…"). A host that renders
672
+ * its own waiting UI can tell them apart: `upcoming` has a kickoff to count
673
+ * down to, `pending` means the match is on and media is seconds away.
666
674
  */
667
- export declare type LiveState = 'live' | 'upcoming' | 'ended' | 'gone';
675
+ export declare type LiveState = 'live' | 'upcoming' | 'pending' | 'ended' | 'gone';
668
676
 
669
677
  export declare interface LiveStateEvent {
670
678
  matchUrn: string;
@@ -680,7 +688,13 @@ export declare interface LiveStateSubscription {
680
688
  close(): void;
681
689
  }
682
690
 
683
- export declare type MatchLiveStatus = 'upcoming' | 'live' | 'ended';
691
+ /**
692
+ * `pending` is the catalog's "kickoff has passed, the stream is being
693
+ * packaged" — not playable yet, `live` expected within seconds to minutes. It
694
+ * is NOT `upcoming` (which has a kickoff ahead) and not `live` (nothing serves
695
+ * yet); `/v1/playback` answers `425` for it without a `liveStartsAt`.
696
+ */
697
+ export declare type MatchLiveStatus = 'upcoming' | 'pending' | 'live' | 'ended';
684
698
 
685
699
  export declare interface MatchStatus {
686
700
  matchUrn: string;
package/dist/index.js CHANGED
@@ -44,7 +44,7 @@ async function s(e) {
44
44
  return t;
45
45
  }
46
46
  function c(e) {
47
- return e === "live" || e === "ended" || e === "upcoming" ? e : "upcoming";
47
+ return e === "live" || e === "ended" || e === "upcoming" || e === "pending" ? e : "upcoming";
48
48
  }
49
49
  //#endregion
50
50
  //#region src/core/http.ts
@@ -1879,7 +1879,7 @@ async function xt() {
1879
1879
  }
1880
1880
  //#endregion
1881
1881
  //#region src/core/version.ts
1882
- var St = "2.9.3", Ct = {
1882
+ var St = "2.10.0", Ct = {
1883
1883
  accent: "#E1B600",
1884
1884
  accentText: "#1B1C23",
1885
1885
  background: "#0e0f13",