commerce
Next.js Commerce
Runs with mockssource: GitHubTypeScriptMITarchived upstreamcommit 3761e52e60df
TypeScript, MIT licensed. The project labels itself: ecommerce, nextjs, react and shopify.
commerce runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Next.js Commerce app builds and runs on Node 20.18.1+pnpm; home page, search, product detail, CMS pages, sitemap, robots.txt, OpenGraph images, cart, and checkout redirect all serve 200 against a schema-correct mock Shopify Storefront API; real Shopify credentials needed for production data.
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 92 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.
- getProducts(), getPages(), getCollection() crash with 500 when Shopify not configured, unlike their guarded siblings2 minutes
- pnpm not available in PATH1 minute
- Node.js 18 too old for Next.js 15 (requires >=20.9)1 minute
- Prettier style violations in components/cart/actions.ts and lib/shopify/index.ts1 minute
- [page]/opengraph-image.tsx crashes 500: page.seo accessed on null page because Next 15 params Promise not awaited1 minute
- [search/collection]/opengraph-image.tsx same pattern1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- Browser end-to-end with Playwright Chromium: home page renders 4 mock products (200); product page shows title Mock Pants, price $55, Related Products section; Add to Cart creates a cart and adds item; cart modal shows Mock Pants qty1 $55; quantity increment +1 updates to qty2 $110 (confirmed via editCartItems mutation); Proceed to Checkout triggers server action redirecting to mock checkout URL. All 12 SSR routes return 200. OpenGraph images are valid PNGs (ffmpeg decoded). Webhook revalidation returns 200/401 correctly. pnpm test exits 0 (prettier check).
- Model tokens used
- 726,733
- Exact commit tested
- 3761e52e60df
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
POST /api/2023-01/graphql.json op=getCart token=mock-token POST /api/2023-01/graphql.json op=getCollectionProducts token=mock-token POST /api/2023-01/graphql.json op=getCollectionProducts token=mock-token ^C exec /bin/sh -lc "cat <<'EOF' EOF' in /work/repo succeeded in 0ms: The repository is now working. The ARGUSIC_RESULT line above captures the full install, fixes, and … tokens used 726,733 The repository is now working. The ARGUSIC_RESULT line above captures the full install, fixes, and …
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 6 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 15 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.
Of the 11 ecommerce projects Argusic has installed and timed, commerce was the 7th fastest to reach a running state, and 9 of 11 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 | Runs with mocks | 92.00 | 0.31 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.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/commerce)Questions
- Does commerce run?
- commerce runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test commerce?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3761e52e60df. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test commerce?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does commerce take to install?
- 15 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 commerce need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing commerce?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does commerce compare with the alternatives?
- Of the 11 ecommerce projects Argusic has installed and timed, commerce was the 7th fastest to reach a running state, and 9 of 11 reached one at all.
- Where is the evidence for commerce?
- 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.