daffodil
Build complex Ecommerce store frontends and connect to any backend https://discord.gg/BdaJVZ53sR
Runssource: GitHubhomepageTypeScriptMITcommit 538c062d7429
TypeScript, MIT licensed. The project labels itself: angular, daffodil, ecommerce, ecommerce platform, hacktoberfest, hacktoberfest2025, magento and pwa.
daffodil runs. An Argusic agent installed it in 49 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With Node 24 downloaded and a no-sandbox ChromeHeadless launcher patched into tools/karma/karma.conf.js, the full nx build succeeds (62 projects), unit test suites run in real Chrome (core 828, cart 1139, product 219, auth 210, search 87, daffio 129, demo 351 all pass), and the built daffio app serves HTTP 200 with a rendered title.
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.
- Karma tests need Chrome but no browser is installed in the container; ChromeHeadless launcher lacks --no-sandbox and crashes in this container25 minutes
- nx build process died mid-stream (log ended with no summary)12 minutes
- System Node is v18.19.1 but .nvmrc requires 24.19 and Angular 21 needs Node >=202 minutes
- Install time
- 49 minutes
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx nx run-many -t build --parallel=2 exited 0 'Successfully ran target build for 62 projects'; npx nx run @daffodil/core:test exited 0 with 'TOTAL: 828 SUCCESS'; @daffodil/cart 1139, @daffodil/product 219, @daffodil/auth 210, @daffodil/search 87, @daffodil/daffio 129, demo 351 (all SUCCESS); curl 127.0.0.1:4200 returned 200 and headless Chrome rendered <title>Daffodil - A frontend toolkit for ecommerce</title>
- Model tokens used
- 2,592,861
- Exact commit tested
- 538c062d7429
- 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.
ChromeHeadlessDebug: {
base: 'ChromeHeadless',
@@ -52,4 +68,4 @@ module.exports = function(config) {
});
return config;
-}
\ No newline at end of file
+}
All verification complete. Final state: install + build succeed, tests run in real headless Chrome,…
tokens used
2,592,861
All verification complete. Final state: install + build succeed, tests run in real headless Chrome,…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 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
- Took 49 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 10 angular projects Argusic has installed and timed, daffodil was the 10th fastest to reach a running state, and 10 of 10 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)
angulardaffodilecommerceecommerce-platformhacktoberfesthacktoberfest2025magentopwatypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/daffodil)Questions
- Does daffodil run?
- Yes. daffodil runs. Argusic installed and launched it on a clean machine in 49 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test daffodil?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 538c062d7429. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test daffodil?
- The run that produced this verdict cost $0.60: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does daffodil take to install?
- 49 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 daffodil need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing daffodil?
- 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.
- How does daffodil compare with the alternatives?
- Of the 10 angular projects Argusic has installed and timed, daffodil was the 10th fastest to reach a running state, and 10 of 10 reached one at all.
- Where is the evidence for daffodil?
- 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.