pwa-kit

React-based JavaScript frontend framework to create a progressive web app (PWA) storefront for Salesforce B2C Commerce.

Runssource: GitHubhomepageJavaScriptBSD-3-Clausecommit 5762377b6ab3

JavaScript, BSD-3-Clause licensed. The project labels itself: ecommerce, javascript, monorepo, nodejs, progressive web app, pwa, react and salesforce.

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

PWA Kit monorepo v3.21.0-dev is fully installed and built. All 13 packages bootstrap successfully. 11 packages with test suites run cleanly except for 3 pre-existing timing-dependent failures in commerce-sdk-react basket mutation tests (customerBaskets.data race condition with nock delay).

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.54 (measured)
recorded runs
1
last tested
stars
364
forks
244
open issues
299
watchers
25
size
476 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.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • commerce-sdk-react: ShopperBaskets/mutation.test.ts has 2 pre-existing timing failures where customerBaskets.data is undefined instead of expected object
  • commerce-sdk-react: ShopperBasketsV2/mutation.test.ts has 1 pre-existing timing failure (same root cause)
Install time
2 minutes
Cold machine to finish
59 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm install succeeded (998 packages, 13 lerna packages bootstrapped). Test suites run package-by-package: pwa-kit-runtime (723/723), pwa-kit-react-sdk (331/331), pwa-kit-dev (112/112), pwa-kit-mcp (174/174), commerce-sdk-react (805/808, 3 pre-existing failures), template-retail-react-app (~3000+ all passing individual files), template-express-minimal (1/1), template-mrt-reference-app (45/45), template-typescript-minimal (1/1), pwa-kit-create-app (no tests), test-commerce-sdk-react (no tests)
Model tokens used
158,503
Exact commit tested
5762377b6ab3
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

| pwa-kit-react-sdk | 31 suites, 331/331 passed |
| pwa-kit-dev | 4 suites, 112/112 passed |
| pwa-kit-mcp | 13 suites, 174/174 passed |
| commerce-sdk-react | 71 suites, 805/808 passed |
| template-retail-react-app | ~538 files, all pass individually |
| template-express-minimal | 1/1 passed |
| template-mrt-reference-app | 45/45 passed |
| template-typescript-minimal | 1/1 passed |
| pwa-kit-create-app | no tests (exits cleanly) |
| test-commerce-sdk-react | no tests (exits cleanly) |
**3 pre-existing failures** in `commerce-sdk-react` — timing-dependent race conditions in `ShopperB…
**One minor issue**: `template-retail-react-app`'s `npm test` via `pwa-kit-dev test` hangs because …

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, faster than the median of the 10 comparable projects Argusic has measured.
  • 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 BSD-3-Clause, 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, pwa-kit was the 3rd 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.
  • 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.54

Topics (from GitHub)

ecommercejavascriptmonoreponodejsprogressive-web-apppwareactsalesforcesalesforce-developersstorefront

Embed the badge

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

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

Questions

Does pwa-kit run?
Yes. pwa-kit runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test pwa-kit?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5762377b6ab3. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test pwa-kit?
The run that produced this verdict cost $0.54: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pwa-kit 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 pwa-kit need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pwa-kit?
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 pwa-kit compare with the alternatives?
Of the 11 ecommerce projects Argusic has installed and timed, pwa-kit was the 3rd fastest to reach a running state, and 9 of 11 reached one at all.
Where is the evidence for pwa-kit?
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