Automation
CLI and standalone bundles
Use every CLI command and package a single-file program as a system tool.
Core commands
Commands that accept an optional file use the current project entry when the file is omitted.
orviscript init [DIRECTORY]
orviscript run [FILE]
orviscript check [FILE]
orviscript fmt [--check] <FILE>
orviscript test [FILE] [--filter TEXT] [--list]
orviscript add <NAME> --path <DIRECTORY>
orviscript remove <NAME>
orviscript install
orviscript depsBuild a standalone executable
build packages the source and OrviScript runtime into one executable with an integrity-checked payload. It is a deployment format, not native AOT compilation.
orviscript build src/main.orvi --output my-tool
./my-tool
orviscript inspect my-toolOutputs are protected
build preserves an existing output unless --force is supplied. inspect reads bundle metadata without executing the program.
orviscript build app.orvi --output app --force
orviscript inspect app