test: update registry consumer dependencies from #2598

[github-actions]

Summary

Classification: expected change. The next-react-tailwind registry consumer fails during its production build because @videojs/react/media/hlsjs-video imports @videojs/hlsjs-video, which is not installed in the generated consumer.

Triggering PR

refactor(html): new @videojs/cdn package

Failed run

• Run: https://github.com/videojs/v10/actions/runs/33799402402
• Head SHA: a75616dfa7c71e992c9d076045654032f7387a74
• Affected test: Registry consumers / next-react-tailwind global setup; no Playwright test executed.

Evidence

• The failed job log records a Next.js/Turbopack module-resolution error in packed @videojs/react/dist/default/media/hlsjs-video/media.js: Can't resolve '@videojs/hlsjs-video'.
• The artifact report was uploaded, but the test-results/trace upload found no files because setup failed before Playwright ran.
• At the failed SHA, @videojs/react lists @videojs/hlsjs-video in peerDependencies, while the registry package closure in apps/e2e/suites/registry/setup/global.ts follows only dependencies and optionalDependencies.
• The fixture overlay imports HlsJsVideo from @videojs/react/media/hlsjs-video; PR refactor(html): new @videojs/cdn package #2598 changes CDN paths in page generation but does not add the adapter to this consumer dependency closure.

Likely cause

Verified facts: the consumer uses the HLS.js media component, its adapter is a peer dependency, and that peer is absent from the packed local registry overrides.

Inference: the adapter becoming an explicit peer dependency is intentional; the external-consumer fixture is stale because it does not declare or install the peer required by the media component it exercises.

Recommended actions

• Update the registry consumer setup or fixture manifest to install/pack @videojs/hlsjs-video when the React HLS.js component is used.
• Keep the consumer test external to the workspace so it verifies that published package peer requirements are satisfied.
• Re-run the Registry consumers job and confirm the generated Next consumer builds before evaluating browser assertions.

[mihar-22]

Resolved. All five registry-consumer issues filed today share one root cause: after the adapter split, @videojs/react/media/hlsjs-video and @videojs/html/media/hlsjs-video import @videojs/hlsjs-video, an optional peer, and the registry-consumer setup only packed regular/optional dependencies.

Fixed in the #2567 rewrite (92b5dc0): apps/e2e/suites/registry/setup/global.ts now packs the adapter via overlayDependencies and adds it to each generated consumer's dependencies, mirroring how a real app installs the peer. Every stacked PR descends from that commit.

Verified: Registry consumers job passed on the new head (https://github.com/videojs/v10/actions/runs/33803726825); locally all 5 consumers built and 5 Playwright tests passed. Closing as duplicates of the same fixed cause.