Reference

Command Line

The zornux command runs, checks, compiles, serves, formats, tests, documents, and debugs your programs — plus an interactive REPL, a package manager, and a language server.

Commands

A quick tour

zornux run hello.zx             # run a program
zornux check app.zx             # validate without running
zornux build app.zx             # compile to app.zxbc
zornux serve product_api.zx     # run + serve a web service
zornux format app.zx --write    # reformat in place
zornux test                     # run the project's tests
zornux doc                      # generate API docs into docs/api
zornux debug app.zx             # interactive debugger
zornux repl                     # interactive session

Options

Diagnostics

Errors are located and beginner-friendly by default:

error ZX0700

file.zx:1:6
show username
     ^^^^^^^^

I don't know what 'username' is — it was never created.
help: create it first, e.g. create username = …

Add --json for the machine-readable diagnostic standard (great for CI and editors).

Security from the command line

--identity, --role, and --permission build the run's security context, so you can test restrict to … locally without a web request.

zornux run guarded.zx                 # anonymous → restricted branch runs
zornux run guarded.zx --role Admin    # authorized → protected code runs

The REPL

State persists across lines, and multi-line blocks keep reading until end:

zornux> create x = 5
zornux> x + 3
8
zornux> function greet with n
...      give back "Hi " + n
...   end
zornux> greet("Ada")
Hi Ada
zornux> exit

Exit codes

Built for scale

Zornux stays fast and predictable as a program grows — from a one-line script to a long-running service. Everyday values are shared where it's safe to, collections and members are looked up once and reused, and recursion and resource use are bounded — so package-heavy projects and object- and query-heavy code hold up under load, without you tuning anything.

Editor support

zornux lsp starts a Language Server that speaks JSON-RPC over stdin/stdout, so any LSP-compatible editor gets live diagnostics, completion, hover, go-to-definition, find references, rename, signature help, document symbols, folding, and semantic highlighting. Point your editor's LSP client at the zornux lsp command for .zx files:

# Example: a minimal VS Code language client
const serverOptions = { command: "zornux", args: ["lsp"] };
const clientOptions = {
  documentSelector: [{ language: "zornux", pattern: "**/*.zx" }],
};

Neovim, Helix, Sublime, and Emacs configure the same command. The server is editor-independent.

Debugging

zornux dap starts a Debug Adapter Protocol server so any DAP editor gets breakpoints, stepping, variable inspection, and watches. zornux debug is an interactive terminal debugger. See the debugger guide.

Projects, packages, tests & docs

Point run, test, doc, and the rest at a directory or a zornux.project file to work on a whole multi-file project. zornux init, add, restore, pack, and publish manage package dependencies and a local registry; zornux test runs your tests; and zornux doc generates API documentation.