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 1.6 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.

Repo installs with yarn 4.1.1; core package builds; CLI builds and compiles .tsx components to React output. Core test suite runs 10211 tests passing; CLI test suite runs 9 tests passing. 32 pre-existing snapshot mismatches (signalsOnUpdate) reproducible regardless of install method.

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

verdict
Runs
Argusic Score
80 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
14,463
forks
677
open issues
178
watchers
96
size
31 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.

  • Yarn 4.1.1 peer dependency warnings (12 packages with version mismatches: prettier 2.8.8 vs ^3.0.0, vite 4.5.0 vs ^5.0.0, react 18.2.0 vs ^16.8.0 etc.) — non-fatal
Install time
2 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
1 hit, 0 fixed with no human help
How the result was proved
yarn vitest run on core: 10211 passed, 32 failed (all pre-existing snapshot mismatches in signalsOnUpdate), 3 skipped in 829s. yarn vitest run on cli: 9 passed, 0 failed in 17.5s. CLI binary: mitosis compile -t react /tmp/test-component.tsx produced valid React JSX output.
Model tokens used
58,651
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.

/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.6, "errors": [{"msg": "Y…
exec
/bin/sh -lc "echo \"ARGUSIC_RESULT:{\\\"install_succeeded\\\":true,\\\"launch_succeeded\\\":true,\\…
 succeeded in 0ms:
/bin/sh: 1: mitosis: not found
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
 succeeded in 0ms:
tokens used
58,651

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 1.6 minutes, faster than the median of the 9 comparable projects Argusic has measured.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Hit 1 error during setup, 1 of which were not solved.

Of the 10 angular projects Argusic has installed and timed, mitosis was the 4th 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.
  • A quick evaluation: it was running 1.6 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 Runner2/3Runs80.000.10
Argusic Runner1/3Runs80.000.09

Topics (from GitHub)

angularbuildercompilerdeclarativefigmajsxjsx-liteliquidno-codereactshopifysolidsolidjssveltevisualvue

Embed the badge

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

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

Questions

Does mitosis run?
Yes. mitosis runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error 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. 2 attempts are 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.10: 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?
1.6 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?
1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
How does mitosis compare with the alternatives?
Of the 10 angular projects Argusic has installed and timed, mitosis was the 4th fastest to reach a running state, and 10 of 10 reached one at all.
Where is the evidence for mitosis?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion