jadpo build
On this page
Build the app to deploy.
Check the project as jadpo check does, then compile each deployable into one native binary in build/target/deployables: in app.jadpo names each one, what it serves and runs and its target; with none declared there is one, app, which runs everything. One built for Target.wasm becomes a WebAssembly module for Cloudflare Workers instead, beside Jadpo's module shim and a wrangler.json naming the settings it needs, its size shown raw and gzipped; the Worker reads its settings from its bindings and serves once its database has every migration. It compiles offline in release with the toolchain and the runtime's lock this Jadpo was built with, keeping each one's Rust in build/rust/
jadpo build [deployable]Arguments
deployable(optional): The deployable to build; every one when left out
On every command
--json: Print data for tools instead of text--help: Show every flag, with examples--color <when>: Choose when to use colour
jadpo build --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("build"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.
Examples
# Build every deployable of the app you are injadpo build# Build one deployablejadpo build kiosk# Print where it was written and its build stamp as datajadpo build --json
Errors
cli.build_arguments: Build command has invalid argumentstoolchain.build_failed: Rust compiler couldn't build the deployabletoolchain.fetch_failed: Rust toolchain or crates couldn't be fetchedtoolchain.artifact_write_failed: Generated file could not be writtentoolchain.project_not_found: Project could not be found
Markdown for agents: /docs/jadpo-build.md.Built from Jadpo main at a707efb.