Generated xgoja binaries can expose JavaScript functions as CLI commands. The build specification declares one or more jsverb sources. At startup, the generated runtime support scans those sources, builds Glazed commands from discovered verb metadata, and attaches them under the configured verbs root command.

A jsverb command executes inside the generated xgoja runtime module set. The command builds field values from CLI flags and arguments, creates a runtime with the top-level modules list, injects the source loader for the scanned JavaScript files, invokes the captured JavaScript function, and prints the Glazed command result.

Source modes

• Runtime filesystem sources read JavaScript files from disk when the generated binary runs.
• Embedded sources are copied into the generated Go module at build time and embedded with go:embed.
• Provider-shipped sources come from a provider package's embedded filesystem.

Use the sources subcommand under the verbs root to list configured source IDs.

Field naming

JavaScript function parameters and verb fields are exposed as idiomatic kebab-case CLI flags while JavaScript invocation still receives the original author-declared names.

For example:

function indexQuery(profilePath, docsJson, foo_bar) {
  return { profilePath, docsJson, foo_bar };
}

__verb__("indexQuery", {
  fields: {
    profilePath: { help: "Profile registry path" },
    docsJson: { help: "JSON document list" },
    foo_bar: { help: "Example snake_case field" }
  }
});

The generated command exposes --profile-path, --docs-json, and --foo-bar, but indexQuery is still called with profilePath, docsJson, and foo_bar argument values.

The same rule applies to fields in named sections. A section field declared as localOnly is exposed as --local-only on the CLI, but a function bound to that section still receives filters.localOnly. jsverbs keeps an explicit mapping between the CLI/Glazed field name and the JavaScript object key.