Fix: build the SPA on install so /draw isn't 'Page not found'

[vibhavkatre]

The bug (reported by @asoral)

Visiting <site>/draw on a fresh install returns Frappe's "Page not found."

Root cause

The SPA's outputs — draw/www/draw.html and draw/public/frontend/ — are git-ignored build artifacts produced by yarn build (via the frappe-ui vite plugin's buildConfig). The app had no root-level package.json, so nothing ran that build during install/deploy. A fresh bench get-app draw (or Frappe Cloud deploy) therefore had no www/draw.html at all, and /draw had nothing to serve → 404.

Fix

Add a root package.json mirroring the pattern every Frappe SPA app uses (Drive, Helpdesk, Gameplan, Insights):

{
  "scripts": {
    "postinstall": "cd frontend && yarn install",
    "build": "cd frontend && yarn build"
  }
}

bench build — run on every Frappe Cloud deploy and self-hosted install — now invokes the app's build script and generates the SPA.

Verified

From a clean tree with both artifacts deleted (simulating a fresh clone):

• bench build --app draw → regenerates www/draw.html + public/frontend/assets/* and /draw serves again. ✅

This also makes Frappe Cloud installs turnkey.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 5/5

Single-file addition that wires up the standard Frappe SPA build hook; no logic changes, no risk of regression.

This adds exactly one file with three scripts that delegate to the existing frontend build. The pattern is battle-tested across multiple Frappe apps, and the change has no effect on any existing code path.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Fix: build the SPA on install/deploy so ..." | Re-trigger Greptile}