/cli-just

Inline Scripts

Read when a recipe needs multi-line shell or another interpreter. Confirm the installed syntax with just --help, just --man, or the current manual before adding an attribute or setting.

Use linewise recipes for short commands. Use [script("interpreter")] or a shebang when the body needs shell state, traps, control flow, or a non-shell language. set default-script changes the default; [shell] opts one recipe back to linewise execution.

[script("bash")]
deploy:
    set -e
    ./build.sh
    ./deploy.sh

Script recipes are quiet already. Do not prefix a [script] recipe with @: there it prints the generated script body. See recipes.md for linewise echo rules.

Bash on macOS

Assume /bin/bash 3.2 unless the recipe selects another shell. Write 3.2-compatible bodies by default; pin a newer interpreter only for semantics that require it, and ensure that path is available in CI and agent environments.

set shell := ["/opt/homebrew/bin/bash", "-euo", "pipefail", "-c"]

For a Bash-4+-only recipe, guard before using its newer syntax:

[script("bash")]
modern:
    if [ "${BASH_VERSINFO[0]}" -lt 4 ]; then
        echo "error: bash >= 4 required (found $BASH_VERSION)" >&2
        exit 1
    fi
    declare -A map=([a]=1)