media-chrome

Custom elements (web components) for making audio and video player controls that look great in your website or app.

Runssource: GitHubhomepageTypeScriptMITcommit 803787e81917

TypeScript, MIT licensed. The project labels itself: audio, audio player, media chrome, mux, ui components, video, video player and web components.

media-chrome runs. An Argusic agent installed it in 2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install succeeds, npm run build produces all dist variants (ESM, CJS, IIFE, React), and the test suite runs in Playwright's Chromium with 620/721 passing tests; 5 playback-dependent tests fail only because no codec is available in the container, and 96 are skipped as expected.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
2,771
forks
129
open issues
1
watchers
28
size
69 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing media-chrome, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • CHROME_PATH environment variable not set — chrome-launcher could not find Chrome1 minute
  • Chromium sandbox crash — 'No usable sandbox' due to container environment0.5 minutes
  • npm run serve livereload fails — 'The feature watch recursively is unavailable on the current platform'0.5 minutes
Install time
2 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm run test:unit with CHROME_PATH set to Playwright Chromium: 620 passed, 5 failed, 96 skipped over 19 test files in 21s; also npm run build exited 0 producing dist/{index.js,cjs,react,iife}
Model tokens used
46,904
Exact commit tested
803787e81917
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'cd /work/repo && CHROME_PATH=/home/runner/.cache/ms-playwright/chromium-1148/chrome-li…
 succeeded in 22222ms:
Chrome: |██████████████████████████████| 0/19 test files | 0 passed, 0 failed
Chrome: |██████████████████████████████| 19/19 test files | 620 passed, 5 failed, 96 skipped
Chrome: |██████████████████████████████| 19/19 test files | 620 passed, 5 failed, 96 skipped
Finished running tests in 21.2s with 5 failed tests.
Here's the final assessment:
ARCUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors…
tokens used
46,904
Here's the final assessment:
ARCUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes, faster than the median of the 17 comparable projects Argusic has measured.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 18 audio projects Argusic has installed and timed, media-chrome was the 3rd fastest to reach a running state, and 15 of 18 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

audioaudio-playermedia-chromemuxui-componentsvideovideo-playerweb-components

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/media-chrome.svg)](https://argusic.com/subject/media-chrome)

Questions

Does media-chrome run?
Yes. media-chrome runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test media-chrome?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 803787e81917. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test media-chrome?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does media-chrome take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does media-chrome need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing media-chrome?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does media-chrome compare with the alternatives?
Of the 18 audio projects Argusic has installed and timed, media-chrome was the 3rd fastest to reach a running state, and 15 of 18 reached one at all.
Where is the evidence for media-chrome?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion