hot-updater
A self-hostable OTA update solution for React Native (Alternative to CodePush)
Runssource: GitHubhomepageTypeScriptNOASSERTIONcommit 35964bb6cf02
TypeScript, NOASSERTION licensed. The project labels itself: expo, plugin system, react native, react native codepush, react native ota, self hosted and supabase.
hot-updater runs. An Argusic agent installed it in 15 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The monorepo builds (26 of 26 projects) with pnpm + Node.js 22, and all 2171 unit tests pass across 170 test files. The hot-updater CLI binary runs and responds to --help. One minor test fix was applied: the supabase migration workdir test's npx mock was patched to work in a clean environment without a pre-populated npx cache.
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 95 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.
- Test `finds staged migrations when npx runs from the workspace root` failed because the mock used `npx --no-install -- node probePath ...` which only works when `node` is already in npx cache — not the case in this clean container.6 minutes
- Node.js v18 lacked `node:util.styleText` required by fumadocs-mdx postinstall script, causing docs postinstall to fail on first pnpm install attempt. Installed pnpm with npm -g (no root).3 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pnpm -w build (nx run-many --target=build) exited 0, building 26 projects; pnpm -w test (vitest run --project=unit:*) exited 0, 2171 passed, 170 test files; node packages/hot-updater/dist/index.mjs --help printed help text with version v0.36.11
- Model tokens used
- 51,264
- Exact commit tested
- 35964bb6cf02
- 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.
date' in /work/repo succeeded in 0ms: Total time check Tue Sep 8 21:35:46 UTC 2026 exec /bin/sh -lc 'echo "start time: 21:20, end time: 21:35" echo "Total: ~15 minutes"' in /work/repo succeeded in 0ms: start time: 21:20, end time: 21:35 Total: ~15 minutes tokens used 51,264
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 15 minutes.
- 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.
- Measured 4 times, so the result is not a one-off.
What did not, or is not known
- Its license file could not be classified automatically, so check it yourself before using it.
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)
expoplugin-systemreact-nativereact-native-codepushreact-native-otaself-hostedsupabase
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hot-updater)Questions
- Does hot-updater run?
- Yes. hot-updater runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test hot-updater?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 35964bb6cf02. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hot-updater?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hot-updater take to install?
- 15 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 hot-updater need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hot-updater?
- 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.
- Where is the evidence for hot-updater?
- All 4 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.