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 18 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 6 TypeScript packages build successfully. The CLI binary runs and accepts commands. The generate command produces Graphback-generated schemas. The integration test passes. The test project generates schema output via generate, but the codegen plugin produces no visible output (it runs without error).

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.08 (measured)
recorded runs
2
last tested
stars
2,019
forks
108
open issues
51
watchers
20
size
7 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 graphql-cli, 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.

  • GraphQL config missing 'graphback' extension for generate command5 minutes
  • Build failed: tsc cannot find module 'yargs' in @graphql-cli/common - @types/yargs was missing2 minutes
Install time
18 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm install exited 0; all 6 packages built with tsc (common, loaders, cli, init, serve, generate); node bin.js --help returned help text; node bin.js generate --backend printed 'Generation successful!'; integration test 'ava tests/workflow.ts' passed (1 test, 520ms)
Model tokens used
307,758
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.

- **Commands**: `generate --backend` prints "Generation successful!" and creates `src/schema/schema…
- **Tests**: The Ava integration test (`tests/workflow.ts`) passes (1 test, 520ms).
tokens used
307,758
Everything works. Let me summarize what I found and did.
**Summary of work done:**
- **Error 1**: `@types/yargs` was listed in root `package.json` but not installed - TypeScript comp…
- **Error 2**: The `generate` command from `graphback-cli` required a `graphback` extension in `.gr…
- **Build**: All 6 packages (`common`, `loaders`, `cli`, `init`, `serve`, `generate`) compile with …
- **CLI**: The `graphql` binary (`packages/cli/dist/bin.js`) runs and shows the `discover` command …
- **Commands**: `generate --backend` prints "Generation successful!" and creates `src/schema/schema…
- **Tests**: The Ava integration test (`tests/workflow.ts`) passes (1 test, 520ms).

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 18 minutes.
  • Recovered from all 2 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.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.08
Argusic Runner1/3Runs100.000.11

Topics (from GitHub)

apollocligraphqlschematerminal

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/graphql-cli.svg)](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 18 minutes, hitting 2 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. 2 attempts are 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.08: 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?
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 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?
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.
Where is the evidence for graphql-cli?
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