26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# ECP-0116: Hosted Web Uses Current MoQ Watch
|
|
|
|
Status: Draft
|
|
|
|
## Problem / context
|
|
|
|
The hosted `every.channel` player was pinned to `@moq/watch@0.2.0`. After the web deploy, live playback subscribed and rendered video but still produced heavy upstream watcher churn (`skipping slow group`) on an announced relay stream. The current npm release is `@moq/watch@0.2.10`.
|
|
|
|
## Decision
|
|
|
|
Move the hosted web player import fallbacks from `@moq/watch@0.2.0` to `@moq/watch@0.2.10` and keep the module version centralized in `app.js`.
|
|
|
|
## Consequences
|
|
|
|
- Hosted playback receives upstream watcher fixes without changing local transport or publisher code.
|
|
- The version remains explicitly pinned and mirrored across esm.sh, jsDelivr, and unpkg fallbacks.
|
|
- If `0.2.10` regresses, rollback is a one-line version restore.
|
|
|
|
## Alternatives considered
|
|
|
|
- Keep `0.2.0`. Rejected because deployed playback still shows watcher churn with the older package.
|
|
- Use an unpinned latest import. Rejected because CDN drift would make playback behavior harder to reproduce.
|
|
|
|
## Rollout / teardown
|
|
|
|
Deploy the updated web asset to Cloudflare and verify the live site loads the `0.2.10` module URL. Teardown is restoring `MOQ_WATCH_VERSION` to `0.2.0`.
|