frontends

Shopware Frontends is a framework for building custom, headless storefronts with Shopware 6.

Runssource: GitHubhomepageTypeScriptMITcommit 5961f55b9f7c

TypeScript, MIT licensed. The project labels itself: astrojs, ecommerce, hacktoberfest, headless, javascript, nextjs, nitro and nuxt.

frontends runs. An Argusic agent hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed, all 5 packages built, all 1021 tests passed across 6 packages (api-client, helpers, api-gen, composables, cms-base-layer, nuxt-module), and the vue-starter-template production server returns HTTP 200 with a fully rendered storefront page.

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
230
forks
86
open issues
76
watchers
26
size
61 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 frontends, 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.

  • Node.js v18.19.1 is too old; project requires Node ^22.19.0 || ^24.11.0 || >=26.0.05 minutes
  • pnpm not available in the environment1 minute
Cold machine to finish
10 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
node templates/vue-starter-template/.output/server/index.mjs && curl -s -o /dev/null -w '%{http_code}' http://localhost:3000 returned 200 with full SSR-rendered HTML page
Model tokens used
247,852
Exact commit tested
5961f55b9f7c
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.

Install time
the run did not report one
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.

# Check what the pnpm run test exit code is and get final summary
pnpm run test 2>&1 | grep -aE "(Tasks:|×|✗|exit|Error.*Tests)" | tail -10' in /work/repo
 succeeded in 307ms:
 Tasks:    13 successful, 13 total
I also see the `pnpm run test` exit code was 0 since the summary says "13 successful, 13 total". No…
```
```
tokens used
247,852
I also see the `pnpm run test` exit code was 0 since the summary says "13 successful, 13 total". No…
```
```

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.
  • 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.

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

Topics (from GitHub)

astrojsecommercehacktoberfestheadlessjavascriptnextjsnitronuxtreactserverlesstailwindcsstypescriptunocssvercelvitepressvuevuejs

Embed the badge

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

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

Questions

Does frontends run?
Yes. frontends runs. Argusic installed and launched it on a clean machine, hitting 2 errors on the way, and recorded the session.
How did Argusic test frontends?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5961f55b9f7c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test frontends?
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.
Does frontends need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing frontends?
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 frontends?
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