web: bump moq-watch to 0.2.0 for live stability

This commit is contained in:
every.channel 2026-02-24 22:40:49 -08:00
parent 3ff5c26fc1
commit 6569cdc4bd
No known key found for this signature in database
2 changed files with 22 additions and 3 deletions

View file

@ -5,9 +5,9 @@
const DEFAULT_RELAY_URL = "https://cdn.moq.dev/anon";
const MOQ_WATCH_MODULE_URLS = [
"https://esm.sh/@moq/watch@0.1.1/element",
"https://cdn.jsdelivr.net/npm/@moq/watch@0.1.1/element/+esm",
"https://unpkg.com/@moq/watch@0.1.1/element.js?module",
"https://esm.sh/@moq/watch@0.2.0/element",
"https://cdn.jsdelivr.net/npm/@moq/watch@0.2.0/element/+esm",
"https://unpkg.com/@moq/watch@0.2.0/element.js?module",
];
const HLS_MODULE_URLS = [
"https://esm.sh/hls.js@1.6.2",

View file

@ -0,0 +1,19 @@
# ECP-0075: Bump Web Watcher To `@moq/watch@0.2.0`
## Context
Production web watchers currently load `@moq/watch@0.1.1`. Under live OTA relay streams, Chromium sessions frequently emit runtime failures (`VideoFrame clone` errors and repeated stream resets), leaving playback stalled even after successful subscribe.
## Decision
Update the web watcher module import set to `@moq/watch@0.2.0` across all CDN fallbacks (`esm.sh`, `jsdelivr`, `unpkg`).
## Rationale
- Keeps the architecture unchanged (same `<moq-watch>` component and parameters).
- Pulls in upstream runtime fixes without introducing new local playback logic.
- Preserves multi-CDN fallback behavior already used for dependency resilience.
## Reversibility
- Roll back by pinning imports back to `0.1.1` if regressions appear.