meta2d.js
Meta2d.js是一个实时数据响应和交互的2d引擎,可用于Web 组态、SCADA,表报、流程图、中控可视化等可视化需求。Meta2d.js is a 2D visualization engine built around data-driven display and dynamic interaction. It can be used to build web SCADA/HMI, reports, flowcharts, control-room dashboards and similar visualizations and so on.
Could not verifysource: GitHubhomepageTypeScriptMITcommit a13bf57ae9ca
TypeScript, MIT licensed. The project labels itself: 2d, 2d engine, canvas, diagram, graph, scada, typescript and visualization.
Argusic could not get meta2d.js running. An Argusic agent installed it in 23 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install and pnpm build complete, all 18 packages compiled to dist/ with index.js outputs, webpack bundle at dist/meta2d.js/meta2d.js (762 KiB, valid JS), es5 example serves all assets at HTTP 200, vue3 example builds with vite to 2.7M dist/
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 80 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.
- pnpm not installed in PATH (needs global install)2 minutes
- pnpm install blocked by ERR_PNPM_IGNORED_BUILDS for esbuild1 minute
- Install time
- 23 minutes
- Cold machine to finish
- 25 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pnpm build exited 0 (18 packages tsc + 1 webpack + copies); python3 HTTP server serving examples/es5 returned 200 on index.html, meta2d.js, index.js, stats.min.js, dialog.js, index.css, btn.svg; node -e 'new Function(code)' confirmed valid JS syntax
- Model tokens used
- 81,910
- Exact commit tested
- a13bf57ae9ca
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
new Function(code);
console.log('meta2d.js: valid JS syntax');
} catch(e) {
console.log('Error:', e.message);
}
\" 2>&1" in /work/repo
succeeded in 224ms:
meta2d.js: valid JS syntax
All checks passed. Here's the final result:
tokens used
81,910
All checks passed. Here's the final result: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
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 23 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 2d projects Argusic has installed and timed, meta2d.js was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
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 | Unverified | 80.00 | 0.14 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/meta2d-js)Questions
- Does meta2d.js run?
- Argusic could not verify that meta2d.js runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test meta2d.js?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a13bf57ae9ca. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test meta2d.js?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does meta2d.js take to install?
- 23 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 meta2d.js need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing meta2d.js?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does meta2d.js compare with the alternatives?
- Of the 6 2d projects Argusic has installed and timed, meta2d.js was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for meta2d.js?
- 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.