causet build compile

Compiles a Causet application from .causet DSL files into IR artifacts: ruleset.vrd, causet.projections.json, causet-sdk-ir.json, and manifest.json.

causet build compile invokes the native Causet compiler. It validates DSL syntax, resolves cross-references between sections, and produces the IR consumed by causet release create.

The real command is causet build compile (a subcommand of build) — there is no bare top-level causet compile. A separate causet dev command wraps the same compiler for a local file-watch loop; see causet dev.

Usage

causet build compile --runtime <path> --out <output-dir>

Example:

causet build compile --runtime ./concert-app --out ./build/concert-app-out

Flags:

Flag	Required	Description
`--runtime <path>`	yes	Path to the folder containing `app.causet`
`--out <path>`	no	Directory to write IR artifacts (default: `dist`)

--rules still works as a hidden, deprecated alias for --runtime.

For lint + validate + compile together, use causet build (no subcommand) or run causet build validate first — see Install Causet and Quickstart.

Output

On success, the CLI prints the platform, output path, artifact size, and paths to the SDK IR and manifest files. Fix any compiler errors before deploying — see Compiler Errors for the full list of VERR_* codes.

CI Usage

Run causet build compile (or the combined causet build) on every pull request before deployment:

# GitHub Actions example
- name: Compile Causet DSL
  run: |
    causet build compile \
      --runtime ./concert-app \
      --out ./build/concert-app-out
 
- name: Upload IR artifacts
  uses: actions/upload-artifact@v3
  with:
    name: causet-ir
    path: ./build/concert-app-out/

A non-zero exit code fails the CI job. Fix all compiler errors before deploying.

What is Causet?