react-h5-audio-player

React audio player component with UI. It provides time indicator on both desktop and mobile devices.

Runssource: GitHubhomepageJavaScriptMITcommit d93969e30aab

JavaScript, MIT licensed. The project labels itself: audio, audio player, music player, react, react audio player and typescript.

react-h5-audio-player runs. An Argusic agent installed it in 9 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

With Node 22.23.3 on PATH, yarn install --frozen-lockfile, yarn build, eslint src, and the vitest suite (123/123 passing) all complete cleanly in /work/repo

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.02 (measured)
recorded runs
1
last tested
stars
694
forks
102
open issues
28
watchers
9
size
13 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 react-h5-audio-player, 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.

  • System Node is v18.19.1, below the project's engines >=20; Node 20 then failed because @testing-library/jest-dom requires node >=229 minutes
Install time
9 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
corepack yarn test exited 0 with 6 files / 123 tests passed; corepack yarn build exited 0 and emitted lib/react-h5-audio-player.min.js; node -e 'require("./lib/index.js")' exported RHAP_UI and default
Model tokens used
61,822
Exact commit tested
d93969e30aab
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 attempt that decided the verdict above. 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.

- The preinstalled system Node was v18.19.1, below the project's `engines` requirement (`>=20`); No…
- `yarn build` produced all five artifacts cleanly: `lib/`, `es/`, `lib/styles.css`, `lib/index.d.t…
- `yarn lint` (without the script's `--fix`) exited 0.
- The built CommonJS entry loads and exports `RHAP_UI` plus the default `AudioPlayer` component.
- No third-party keys, network services, or mocks were needed; the test suite covers the player log…
**Result Driven**
- Verified commands: `corepack yarn test` → `vitest --run` exited 0, 6 test files and 123 tests pas…
- Install duration was approximately 9 minutes, dominated by downloading the Node 22 toolchain.
**Summary**
- Install, build, lint, and full test suite (123/123) all pass under Node 22.23.3.
- Root cause fixed: system Node v18 (and v20) didn't meet the project's `engines`/dependency requir…
- No credentials or mocks were needed — this is a pure client-side React library.

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 9 minutes.
  • Recovered from all 1 error 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 18 audio projects Argusic has installed and timed, react-h5-audio-player was the 9th 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 9 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 Runner1/3Runs100.000.02

Topics (from GitHub)

audioaudio-playermusic-playerreactreact-audio-playertypescript

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/react-h5-audio-player.svg)](https://argusic.com/subject/react-h5-audio-player)

Questions

Does react-h5-audio-player run?
Yes. react-h5-audio-player runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test react-h5-audio-player?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d93969e30aab. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test react-h5-audio-player?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does react-h5-audio-player take to install?
9 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 react-h5-audio-player need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing react-h5-audio-player?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does react-h5-audio-player compare with the alternatives?
Of the 18 audio projects Argusic has installed and timed, react-h5-audio-player was the 9th fastest to reach a running state, and 15 of 18 reached one at all.
Where is the evidence for react-h5-audio-player?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion