next-ecommerce

:zap: Quantum Ecommerce. Made with Next.js | GraphQL | Apollo Server | Apollo Client | SSR

Runssource: GitHubhomepageJavaScriptMITcommit 42630219b6ba

JavaScript, MIT licensed. The project labels itself: apollo, commerce, e commerce, ecommerce, graphql, next js, nextjs and nodejs.

next-ecommerce runs. An Argusic agent installed it in 2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

In dev mode (next dev, SQLite), the app runs and serves the home, product, category, cart, wishlist, and login pages at HTTP 200, and GraphQL sign-up, authenticated session, product/category/search queries, and add-to-cart all return HTTP 200 with real data; production mode still fails for authenticated mutations because its kvexfile config points at an unconfigured MySQL server.

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.04 (measured)
recorded runs
1
last tested
stars
480
forks
138
open issues
9
watchers
12
size
3 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 next-ecommerce, 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.

  • yarn is not installed in the container (README install step uses yarn)1 minute
  • next build exit code misread as failure because sh lacks ${PIPESTATUS}1 minute
  • npm run start with NODE_ENV=production returns connect ECONNREFUSED 127.0.0.1:3306 on authenticated mutations, because knexfile production config points at an unconfigured MySQL host1 minute
Install time
2 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
curl -X POST localhost:3000/api/graphql with products query returned HTTP 200 and 30 products; signUp returned user 35a91bcc; viewer query with session cookie returned the same user; addToCart returned {itemCount:2, subtotal:501.04}; /, /product/1, /category/1, /cart, /wishlist, /user/login all returned HTTP 200; npm run build exited 0; npm run start served / and /checkout with HTTP 200
Model tokens used
165,120
Exact commit tested
42630219b6ba
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.

> [email protected] dev
> next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Loaded env from /work/repo/.env.local
event - compiled client and server successfully in 535 ms (510 modules)
wait  - compiling /api/graphql (client and server)...
event - compiled successfully in 101 ms (91 modules)
^C
Setup, run, and verification are complete. The full README flow works in this container: env file r…
tokens used
165,120
Setup, run, and verification are complete. The full README flow works in this container: env file r…

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 2 minutes.
  • Recovered from all 3 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.
  • A quick evaluation: it was running 2 minutes after the clone.

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 Runner1/3Runs100.000.04

Topics (from GitHub)

apollocommercee-commerceecommercegraphqlnext-jsnextjsnodejsvercel

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/next-ecommerce.svg)](https://argusic.com/subject/next-ecommerce)

Questions

Does next-ecommerce run?
Yes. next-ecommerce runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test next-ecommerce?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 42630219b6ba. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test next-ecommerce?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does next-ecommerce take to install?
2 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 next-ecommerce need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing next-ecommerce?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for next-ecommerce?
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.

Discussion