jolter <command> --help to inspect the syntax shipped by your installed version.
Global options
| Option | Purpose |
|---|---|
--no-progress | Disable the in-place progress line and use stable action lines |
--no-color | Disable ANSI styling |
-q, --quiet | Suppress operational progress while retaining results |
-v, --verbose | Include transfer timing and additional operational detail |
-h, --help | Print help |
-V, --version | Print the Jolter version |
--quiet and --verbose conflict. CI detection, redirected output, and JOLTER_NO_PROGRESS also disable the in-place renderer.
Request syntax
Runtime and tool requests use<name>@<selector>:
jolter setup
auto is the default.
jolter use
use resolves, installs or reuses, and globally activates the exact version. For a built-in tool, an active Node.js runtime is required. For a plugin tool, a provider plugin must already be installed.
When run without a target in an interactive terminal, Jolter can prompt for a runtime or tool.
jolter pin
jolter.json in the current directory. Runtime pinning replaces the previous runtime. Tool pinning preserves the runtime and other tools.
Plugin-provided tool pinning records both the tool and provider plugin when Jolter can identify the provider.
jolter update
Aliases: up.
--all updates every active runtime, built-in tool, and plugin tool sequentially.
jolter list
Aliases: ls.
* marks globally active versions. ready means the expected executable or entry point exists.
jolter doctor
jolter sync
--yes permits Jolter to install missing project plugins.
jolter repair
jolter plugin
JOLTER_HOME/plugins.
jolter uninstall
Aliases: remove, rm.
--force is passed.
jolter prune
jolter cache
status reports cached metadata and download file counts and size. clean removes metadata and downloaded archives, but not installed versions, shims, active selections, or lock files.
jolter setup-ci
GITHUB_PATH and writes outputs when GITHUB_OUTPUT is available.
jolter completions
Aliases: c, comp.
Exit and stream contract
- Successful commands return exit code
0. - Parsing, installation, configuration, storage, and failed health checks return a nonzero exit code.
- Final human results and JSON are written to standard output.
- Progress and failures are written to standard error.
- Machine-output commands suppress decorative progress.