Repository navigation
Conversation
The README's from-source path is `git clone` → `pip install -e .` →
`./build-dashboard.sh`, but the script goes straight to `npm run build`. A
fresh clone has no node_modules, so the build stops at
> vite build
'vite' is not recognized as an internal or external command
and the server keeps serving the "dashboard not built" page. Running
`npm ci` by hand first is what actually makes it work, so the script now does
that itself when node_modules has no vite binary (`npm install` when there is
no lockfile).
Verified on a clean tree: with node_modules moved aside the old script fails
as above; the patched script installs and finishes with "Built:
index-*.js index-*.css", and the running server picks the build up.
Assisted-by: Claude Code / claude-opus-5
Machine: A-2022BAYAREA
Account: tonydzi
Operator: anton
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What breaks
The README's from-source path is:
On a fresh clone the last step fails immediately, because the script calls
npm run buildwithout ever installing the dashboard's dependencies:set -estops there, nothing is built, andthe-lab .keeps serving the "dashboard not built" page — which reads like a packaging problem rather than a missingnpm ci.The fix
Install first when
node_modules/.bin/viteis absent:npm ciwhenpackage-lock.jsonis present (it is),npm installotherwise. Repeat runs are unchanged — the check is a no-op once deps exist.Evidence
Clean tree (node_modules moved aside), same machine, Node 24.17:
'vite' is not recognized,the_lab/staticuntouched✓ built in 5.85s→Built: index-C76cyvdh.js index-BCMOE9h2.css, dashboard live on the running serverContext
Found while setting The Lab up on Windows 11 and running a real four-idea experiment loop on
optimization/test_project(composite score 0.0657 → 1.6587). The API and the worktree isolation worked out of the box; this was the one step in the documented install that needed a manual command.— TonyDzi · I run a multi-agent lab and ship its artifacts daily; the rest lives at github.com/tonydzi — DMs open.