graphql-cli
📟 Command line tool for common GraphQL development workflows
Runssource: GitHubhomepageTypeScriptMITcommit aa709566b74a
TypeScript, MIT licensed. The project labels itself: apollo, cli, graphql, schema and terminal.
graphql-cli runs. An Argusic agent installed it in 16 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
graphql-cli v5.0.0 builds all 6 core packages, the CLI binary works (--help, --version, discover all succeed), and the integration test passes using real generate and codegen commands against a local schema project.
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
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.
- @graphql-cli/common type error: root @graphql-tools/utils v8 Loader incompatible with @graphql-tools/load's nested v7 loader types7 minutes
- UrlLoader type mismatch: DocumentLoader.load() returns Promise<Source> but Loader expects Promise<Source[]>4 minutes
- yarn not in PATH while lerna.json configured for yarn3 minutes
- website build failed: ERR_OSSL_EVP_UNSUPPORTED on Node 18 with webpack2 minutes
- Install time
- 16 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- lerna run test passed, 1 test passed (integration/Test cli workflow); node packages/cli/dist/bin.js --help returned usage; --version returned 5.0.0; discover subcommand exited 0
- Model tokens used
- 189,580
- Exact commit tested
- aa709566b74a
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
lerna info Executing command in 1 package: "yarn run test" lerna info run Ran npm script 'test' in 'graphql-cli-integration-test' in 1.9s: yarn run v1.22.22 $ ava ✔ Test cli workflow (447ms) ─ 1 test passed Done in 1.72s. lerna success run Ran npm script 'test' in 1 package in 1.9s: lerna success - graphql-cli-integration-test tokens used 189,580
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 16 minutes.
- Recovered from all 4 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/graphql-cli)Questions
- Does graphql-cli run?
- Yes. graphql-cli runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test graphql-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit aa709566b74a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test graphql-cli?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does graphql-cli take to install?
- 16 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 graphql-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing graphql-cli?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for graphql-cli?
- 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.