mern-marketplace
A MERN stack based online marketplace application [Full-Stack React Projects]
Runssource: GitHubhomepageJavaScriptMITcommit bf3fc45e7782
JavaScript, MIT licensed. The project labels itself: ecommerce, expressjs, full stack, mern, mern stack, mongodb, nodejs and reactjs.
mern-marketplace runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The MERN Marketplace runs on MongoDB 7.0.14 plus Node 18 with the --openssl-legacy-provider flag: the development server and a production build both serve the app (HTTP 200), and signup, signin, shop, product, and live-auction bidding all work end to end against the local database.
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.
- webpack 4 build crashes on Node 18/OpenSSL 3 with ERR_OSSL_EVP_UNSUPPORTED (MD4 hash unsupported)5 minutes
- MongoDB 4.2.24 prebuilt binary fails to load: libcrypto.so.1.1 not found on Ubuntu 24.04 (OpenSSL 3 only)4 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run development (with NODE_OPTIONS=--openssl-legacy-provider) printed 'Server started on port 3000.' and 'Compiled successfully'; curl localhost:3000 returned 200 with SSR HTML; full signup->signin->create shop/product/auction flow persisted in MongoDB; socket.io test emitted bid 150 and received 'new bid' event with top bid 150, confirmed in DB; npm run build exited 0; PORT=3001 node dist/server.generated.js answered 200
- Model tokens used
- 309,987
- Exact commit tested
- bf3fc45e7782
- 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.
- Real API flow against real MongoDB: signup → 200 `Successfully signed up!`; signin → 200 with JWT… - Product flow: create product → 200; `GET /api/products/latest` → 200 list; product image endpoint… - Auction flow: create auction → 200; `GET /api/auctions` and `GET /api/auction/:id` → 200; real-ti… - Auth guard: `POST /api/orders/:userId` without token → HTTP 401 as designed; `GET /api/order/stat… - All main pages (`/signup`, `/signin`, `/shops/all`, `/product/:id`, `/auction/:id`, `/cart`, `/us… - Production mode: `NODE_OPTIONS=--openssl-legacy-provider npm run build` → exit 0 (`dist/server.ge… - Both servers and mongod still up at end of session **Known gaps** - No test suite exists in the project (no test script, zero test files), so the app itself was exer… - Stripe checkout: `stripeCustomer`/`createCharge` call Stripe's real test API; no creds are presen… - No browser binary available in the container, so client JS hydration wasn't visually checked; SSR… - Node 18 (container's Node) is newer than the README's Node 13.12.0, which is why the `--openssl-l…
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 12 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 ecommerce projects Argusic has installed and timed, mern-marketplace was the 6th fastest to reach a running state, and 9 of 11 reached one at all.
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)
ecommerceexpressjsfull-stackmernmern-stackmongodbnodejsreactjsweb-application
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mern-marketplace)Questions
- Does mern-marketplace run?
- Yes. mern-marketplace runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test mern-marketplace?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bf3fc45e7782. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mern-marketplace?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mern-marketplace take to install?
- 12 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 mern-marketplace need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mern-marketplace?
- 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 mern-marketplace compare with the alternatives?
- Of the 11 ecommerce projects Argusic has installed and timed, mern-marketplace was the 6th fastest to reach a running state, and 9 of 11 reached one at all.
- Where is the evidence for mern-marketplace?
- 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.