sequential-workflow-designer
Customizable no-code component for building flow-based programming applications or workflow automation. 0 external dependencies. Check out https://nocode-js.com
Runssource: GitHubhomepageTypeScriptMITcommit 842e3b251233
TypeScript, MIT licensed. The project labels itself: agent builder, agentflow, ai designer, automation, component, designer, flow based programming and flowchart.
sequential-workflow-designer runs. An Argusic agent installed it in 25 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.
Core designer builds completely (lib/cjs, lib/esm, dist/umd) and passes all 112 unit tests via karma+jasmine on Chrome Headless 130.
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 96.7 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-typescript-es6-transform incompatible with Babel v7 — missing noIndentInnerCommentsHere()8 minutes
- ReturnType<typeof setTimeout> type mismatch with TypeScript 4.6.4 (returns Timeout not number)2 minutes
- window.structuredClone not recognized by TS lib target2 minutes
- ChromeHeadless needs --no-sandbox flag in container2 minutes
- Karma coverage instrumentation fails with Babel v72 minutes
- Angular and Svelte subproject builds fail (environment deps)
- Install time
- 25 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 6 hit, 5 fixed with no human help
- How the result was proved
- cd /work/repo/designer && CHROME_BIN=... yarn test:single -> 112 SUCCESS, 0 FAILED, 0 ERROR
- Model tokens used
- 182,602
- Exact commit tested
- 842e3b251233
- 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.
The core library builds, exports correctly, and passes all 112 tests. Let me now create a summary. Here's what I found and fixed: **Errors fixed:** 1. **`ReturnType<typeof setTimeout>` type mismatch** (`/work/repo/designer/src/workspace/workspace.… 2. **`window.structuredClone` not on `Window` type** (`/work/repo/designer/src/core/object-cloner.t… 3. **`karma-typescript-es6-transform` incompatible with Babel v7** — The installed babel v7 drops `… 4. **Chrome requires `--no-sandbox`** — Added `customLaunchers` entry with the flag. 5. **Coverage instrumentation also uses Babel v7** — Disabled instrumentation. **Verification:** - `yarn build` in `/work/repo/designer` — builds `lib/cjs/index.cjs`, `lib/esm/index.js`, `dist/ind… - `npm run test:single` in designer — **112/112 SUCCESS** in 0.6s with Chrome Headless 130 - CJS module loads in Node.js with 58 exported symbols
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 25 minutes.
- 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
- Hit 6 errors during setup, 1 of which were not solved.
- 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
Topics (from GitHub)
agent-builderagentflowai-designerautomationcomponentdesignerflow-based-programmingflowchartflowchartsjavascriptlowcodeno-codenocodereactjstypescriptworkflowworkflow-automationworkflow-builderworkflow-designer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sequential-workflow-designer)Questions
- Does sequential-workflow-designer run?
- Yes. sequential-workflow-designer runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test sequential-workflow-designer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 842e3b251233. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sequential-workflow-designer?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sequential-workflow-designer take to install?
- 25 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 sequential-workflow-designer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sequential-workflow-designer?
- 6 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for sequential-workflow-designer?
- 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.