Description
Build and dependency installation are only offered as one-time steps in the initial setup checklist. Once a site has been set up, a contributor who edits files, or who adds a dependency to package.json, has no way to run a build or an install again — the checklist buttons read "Build complete" / "Dependencies installed" and are permanently disabled, and the checklist itself disappears entirely once the setup wizard has been finished.
Rebuilds only happen as part of updating to trunk or applying someone else's patch, neither of which is triggered by your own work. The app's terminal does accept npm install and npm run build, but nothing in the interface points at it.
Step-by-step reproduction instructions
- Create a site and complete the setup checklist through "Start dev server and finish the wizard".
- Stop the dev server and edit any file in the site's
wordpress-develop checkout.
- Look for a way to rebuild — the checklist is gone, and no build control exists anywhere in the site view.
- Add a dependency to
package.json and look for a way to install it — same result.
Operating system
macOS
App version
0.1.2
Technical notes
src/renderer/setup-steps.cjs:44 — install.disabled includes installOk, so the button dies as soon as node_modules/ exists and the last install didn't fail. Changes to package.json don't affect that condition.
src/renderer/setup-steps.cjs:49 — build.disabled includes hasBuilt, which is just fs.existsSync(distDir) (src/main.js:782).
src/renderer/index.jsx:2580 — the checklist renders only when !skipInit, and finishing the wizard sets that flag, so after normal onboarding there is no control at all.
- Re-runs exist only inside the trunk-update (
src/renderer/index.jsx:1790) and apply-patch (src/renderer/index.jsx:1859) chains.
- The working escape hatch: the embedded terminal's
npm install / npm run build (src/renderer/index.jsx:1406-1469, allowlist src/renderer/index.jsx:28).
- Partial mitigation for the build half only: a running dev server runs
grunt _watch (src/renderer/dev-server-command.cjs:28), so JS/CSS edits rebuild on save. Nothing mitigates the install half.
Description
Build and dependency installation are only offered as one-time steps in the initial setup checklist. Once a site has been set up, a contributor who edits files, or who adds a dependency to
package.json, has no way to run a build or an install again — the checklist buttons read "Build complete" / "Dependencies installed" and are permanently disabled, and the checklist itself disappears entirely once the setup wizard has been finished.Rebuilds only happen as part of updating to trunk or applying someone else's patch, neither of which is triggered by your own work. The app's terminal does accept
npm installandnpm run build, but nothing in the interface points at it.Step-by-step reproduction instructions
wordpress-developcheckout.package.jsonand look for a way to install it — same result.Operating system
macOS
App version
0.1.2
Technical notes
src/renderer/setup-steps.cjs:44—install.disabledincludesinstallOk, so the button dies as soon asnode_modules/exists and the last install didn't fail. Changes topackage.jsondon't affect that condition.src/renderer/setup-steps.cjs:49—build.disabledincludeshasBuilt, which is justfs.existsSync(distDir)(src/main.js:782).src/renderer/index.jsx:2580— the checklist renders only when!skipInit, and finishing the wizard sets that flag, so after normal onboarding there is no control at all.src/renderer/index.jsx:1790) and apply-patch (src/renderer/index.jsx:1859) chains.npm install/npm run build(src/renderer/index.jsx:1406-1469, allowlistsrc/renderer/index.jsx:28).grunt _watch(src/renderer/dev-server-command.cjs:28), so JS/CSS edits rebuild on save. Nothing mitigates the install half.