Framework detection, monorepos, environment variables, build commands, and output
Compatibility depends on the selected project root producing static web output that Capacitor can bundle.
What this does
Shows evidence for Vite, CRA, Angular, Vue, static SvelteKit, Next static export, and plain HTML while identifying server-required applications.
What you need
A build script, supported Node version, dependency manifest, and correct output directory.
What LaunchLayer automates
Lockfile priority, safe command selection, framework hints, candidate-root discovery, and environment-variable references found in inspected files.
What remains external
Secret values, framework-specific corrections, and choosing among multiple monorepo roots.
Exact setup steps
Select the project root, package manager, approved install/build commands, Node 18/20/22, output directory, and required variable names.
How to verify it
Run the same build at the exact commit and confirm the output directory exists and is nonempty.
Common failures
Missing lockfile, missing build script, wrong root, incorrect dist/build/out path, SSR dependency, or missing environment value.
Security considerations
Arbitrary shell strings are rejected; secret values belong in protected GitHub environments or secrets.
Related articles
GitHub source builds; ZIP source ingestion; Cloud Build stages.