mitosis
Write components once, run everywhere. Compiles to React, Vue, Qwik, Solid, Angular, Svelte, and more.
Runssource: GitHubhomepageTypeScriptMITcommit cb1e2105c219
TypeScript, MIT licensed. The project labels itself: angular, builder, compiler, declarative, figma, jsx, jsx lite and liquid.
mitosis runs. An Argusic agent installed it in 0.9 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
Mitosis core engine (0.14.0), CLI, and eslint-plugin install, build, and pass 10335 tests; 32 pre-existing snapshot failures affect signals-onUpdate generation and findSignals parsing across all targets
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 80 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.
- @builder.io/e2e-app-qwik build: TS2551 Property 'value' does not exist on type 'string[]' in generated signal-item-list.tsx
- @builder.io/e2e-angular build: TS2551 Property 'value' does not exist on type 'string[]' in generated signal-item-list.ts
- @builder.io/mitosis-fiddle build: Node.js OOM during Next.js SSR build
- @builder.io/mitosis-site build: Node.js OOM during Qwik SSR build
- core test: 32 snapshot mismatches (31x signalsOnUpdate, 1x findSignals)
- Install time
- under a minute
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 5 hit, 0 fixed with no human help
- How the result was proved
- node packages/cli/bin/mitosis --version returned 0.14.0; piping a component through compile -t react produced valid JSX output; yarn ci:test ran 10246 core tests + 9 cli tests + 115 eslint-plugin tests
- Model tokens used
- 266,843
- Exact commit tested
- cb1e2105c219
- 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.
**Install:** `yarn install` completed (warnings only, 52s). **Build:** Core packages (`@builder.io/mitosis`, `@builder.io/mitosis-cli`, `@builder.io/eslint-plu… **CLI verification:** `node packages/cli/bin/mitosis --version` returned `0.14.0`. Pipelines a Mito… **Test suite:** ran via `yarn ci:test`. eslint-plugin: 18/18 files, 115/115 passed. CLI: 4/4 files,… tokens used 266,843 Now I have all the data needed. Let me compile the final report. Here is my complete assessment: **Install:** `yarn install` completed (warnings only, 52s). **Build:** Core packages (`@builder.io/mitosis`, `@builder.io/mitosis-cli`, `@builder.io/eslint-plu… **CLI verification:** `node packages/cli/bin/mitosis --version` returned `0.14.0`. Pipelines a Mito… **Test suite:** ran via `yarn ci:test`. eslint-plugin: 18/18 files, 115/115 passed. CLI: 4/4 files,…
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 0.9 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 5 errors during setup, 5 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.
- A quick evaluation: it was running 0.9 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
Topics (from GitHub)
angularbuildercompilerdeclarativefigmajsxjsx-liteliquidno-codereactshopifysolidsolidjssveltevisualvue
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mitosis)Questions
- Does mitosis run?
- Yes. mitosis runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test mitosis?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cb1e2105c219. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mitosis?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mitosis take to install?
- 0.9 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 mitosis need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mitosis?
- 5 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for mitosis?
- 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.