A generated xgoja binary is a normal Go command-line program built from an xgoja.yaml file. It imports selected provider packages, registers their native Goja modules, embeds a normalized runtime specification, and creates commands that execute JavaScript against named runtime profiles.

A runtime profile selects which provider modules are available to a command invocation. Commands such as eval, run, repl, and mounted JavaScript verbs create a fresh runtime for the selected profile, execute the requested JavaScript, and close the runtime afterwards. The repl command is the rich interactive terminal REPL, while eval is one-shot string evaluation.

Common commands

• modules lists provider modules compiled into the binary.
• eval or the configured evaluation command evaluates one JavaScript source string.
• run executes a JavaScript file with the selected runtime profile and script-local module roots.
• repl starts an interactive Bubble Tea REPL backed by the selected runtime profile.
• verbs or the configured verbs command exposes JavaScript verbs from configured sources.
• help lists bundled runtime help topics.

Runtime profile selection

Commands that execute JavaScript accept or derive a runtime profile. The profile controls require() visibility. If a module is compiled into the binary but is not selected by the runtime profile, JavaScript code in that command cannot require it.

A runtime may select the same provider module more than once under different as names. as is the actual require() name, not an additional alias. For example, generated binaries that embed assets commonly register name: fs twice: as: fs:assets for read-only embedded files and as: fs:host for explicitly allowed host filesystem access. In that setup require("fs") is unavailable unless the runtime also registers an instance whose alias is exactly fs.