pixijs
The HTML5 Creation Engine: Create beautiful digital content with the fastest, most flexible 2D WebGL renderer.
Runssource: GitHubhomepageTypeScriptMITcommit 75865b2a3459
TypeScript, MIT licensed. The project labels itself: canvas, canvas2d, data visualization, game, glsl, javascript, pixi and pixijs.
pixijs runs. An Argusic agent installed it in 18 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PixiJS library builds successfully and hundreds of unit tests pass using electron runner under Xvfb.
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 97.3 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- .mts TypeScript scripts can't run on Node 185 minutes
- npm install blocked by engine-strict=true requiring Node 24+1 minute
- Rollup config uses `with { type: 'json' }` unsupported on Node 181 minute
- exports.mts requires fs-extra/esm (ESM-only) from CJS1 minute
- Electron sandbox prevents test execution1 minute
- GlobalSetup imports ESM-only get-port module1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 81 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npm run build:lib exited 0, created lib/ in 4s. Jest unit tests on multiple categories passed: src/color (18), src/maths (150), src/utils (48), src/extensions (13), src/events (65), src/gif|prepare (34), src/compressed-textures (63), src/spritesheet (87), src/assets (88), src/filters (31), src/app (15), src/scene/sprite|container|graphics|mesh (hundreds+). Total: 100+ test suites, 800+ tests passing.
- Model tokens used
- 361,777
- Exact commit tested
- 75865b2a3459
- 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 3, 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.
3. **Rollup config used `with { type: 'json' }` syntax** — Node 18 doesn't support this; changed to…
4. **Exports script imported `fs-extra/esm` (ESM-only)** — Changed to `require("fs-extra")` (CJS).
5. **Electron sandbox blocked test runner** — Set `JEST_ELECTRON_NO_SANDBOX=true` to pass `--no-san…
6. **Tests needed sequential execution** — Electron runner struggles with parallelism in this envir…
7. **GlobalSetup imports ESM-only `get-port`** — Set `GITHUB_ACTIONS=true` to bypass the globalSetu…
**Verified state:**
- `npm install` completed successfully
- `node scripts/build.cjs --lib --dev` built the library to `lib/` in ~4 seconds
- Jest unit tests run via the `@pixi/jest-electron` runner (Electron v32.1.2 over Xvfb :99)
- Multiple test categories verified: color (18), math (150), ticker, utils (48), extensions (13), e…
- A few pre-existing text metric failures exist due to platform font differences (not fixable here)
- Some GPU/WebGL rendering tests (Extract, RenderTarget, Renderer) hang — these likely need real GPUReplay 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 18 minutes.
- Recovered from all 7 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 4 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.27 | |
| Argusic Runner | 3/3 | Runs | 100.00 | 0.36 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.34 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.16 |
Topics (from GitHub)
canvascanvas2ddata-visualizationgameglsljavascriptpixipixijsrendererrenderingrendering-2d-graphicsrendering-enginewebgl
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pixijs)Questions
- Does pixijs run?
- Yes. pixijs runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test pixijs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 75865b2a3459. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pixijs?
- The run that produced this verdict cost $0.36: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pixijs take to install?
- 18 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 pixijs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pixijs?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pixijs?
- All 4 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.