Getting started
Install neoc and run a first Luau script. Assumes a working CLI and basic Lua familiarity.
Installation
Pre-built binaries for Linux x86_64 and Windows x86_64 on the GitLab Package Registry.
Linux x86_64
curl -fsSL https://gitlab.beluga-sirius.ts.net/api/v4/projects/13/packages/generic/neoc/v0.1.0/install.sh | shDownloads binary, places in $NEOC_INSTALL_DIR (default ~/.neoc/bin). Add to $PATH if needed.
Windows x86_64
Download .exe from releases:
https://gitlab.beluga-sirius.ts.net/api/v4/projects/13/packages/generic/neoc/v0.1.0/neoc-x86_64-pc-windows-gnu.exeRename to neoc.exe, place on PATH.
From source
cargo install --path .Environment variables
NEOC_INSTALL_DIR : Install directory. Default: ~/.neoc/bin.
Running a script
Luau scripts are .luau files. The binary takes file paths or glob patterns, runs each match independently.
First script
print("hello, neoc")neoc hello.luauOutput: hello, neoc\n
Multiple scripts
neoc 'tests/**/*.test.luau'Shell quoting prevents shell expansion; neoc expands the glob internally.
Execution model
Each script runs in its own Luau VM. Runtime maintains a worker pool, dispatches scripts across it. Globals, locals, and userdata are private to each worker. Cross-worker state only via explicit std:workers surface.
See The sandboxing model for rationale and implications.