vike

(Replaces Next.js/Nuxt) 🔨 Build mission-critical applications with stability and development freedom.

Runssource: GitHubhomepageTypeScriptMITcommit b163fd9a896e

TypeScript, MIT licensed. The project labels itself: full stack, node, react, react ssr, server rendering, server side rendering, solid and solid ssr.

vike runs. An Argusic agent installed it in 41 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Vike monorepo installs and builds with Node 20/pnpm 9.15.9, its full test suite (unit, vitest e2e, type tests, and 90 @brillout/test-e2e suites) passes, and the react-full example dev server answers HTTP 200 on / and /star-wars/1.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
2
last tested
stars
5,840
forks
398
open issues
89
watchers
15
size
49 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.

Time lost to each failure while testing vike, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • docs preview e2e crashed with 'JavaScript heap out of memory' (exit 134) during docs build under Node's default 2GB V8 heap6 minutes
Install time
41 minutes
Cold machine to finish
45 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pnpm test:units -> vitest --project unit: 38 files, 207 tests passed; pnpm exec vitest run --project e2e: 6 files, 12 tests passed; pnpm test:types: all 30 tsconfigs passed; pnpm exec test-e2e (NODE_OPTIONS=--max-old-space-size=6144): 90 suites PASS, 0 FAIL; curl -s -o /dev/null -w %{http_code} http://localhost:3000/ returned 200 and http://localhost:3000/star-wars/1 returned 200
Model tokens used
403,647
Exact commit tested
b163fd9a896e
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.

403,647
All verification is complete. Here's the final report.
**Summary**
Ran the Vike monorepo (`[email protected]`) as a fresh user inside this container:
- **Install**: system Node was v18 (repo requires >=20), so I installed Node v20 locally in `~/.loc…
- **Unit tests**: `vitest --project unit` → 38 files / 207 tests passed.
- **Vitest e2e project**: 6 files / 12 tests passed.
- **Type tests**: `test-types` all 30 tsconfigs passed.
- **`@brillout/test-e2e` sweep**: 90 test suites passed with zero failures (all of `examples/`, `te…
- **App launch**: `pnpm run dev` in `examples/react-full` started Vike v0.4.266/Vite v7.3.1; `curl`…
**Error recorded**
- `docs` preview e2e crashed with "JavaScript heap out of memory" (exit 134) under Node's default 2…

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 41 minutes.
  • Recovered from all 1 error 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.
  • Measured 2 times, so the result is not a one-off.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.17
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

full-stacknodereactreact-ssrserver-renderingserver-side-renderingsolidsolid-ssrssrstatic-site-generatorvitevite-pluginvite-ssrvitejsvuevue-ssrweb-framework

Embed the badge

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

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

Questions

Does vike run?
Yes. vike runs. Argusic installed and launched it on a clean machine in 41 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test vike?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b163fd9a896e. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test vike?
The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does vike take to install?
41 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 vike need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing vike?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for vike?
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