Skip to content
On this page

CLI workflows

Use vesty commands for repeatable project operations.

Discover commands

Bash
vesty --helpvesty package --helpvesty release-check --help

Create a project

First complete the source installation and set VESTY_SOURCE. Registry packages are not published yet.

Bash
vesty templatesvesty new my-plugin --template gain --vesty-path "$VESTY_SOURCE/crates/vesty"vesty new my-plugin-ui --template web-ui-param-demo \  --vesty-path "$VESTY_SOURCE/crates/vesty" \  --plugin-ui-path "$VESTY_SOURCE/packages/plugin-ui"

Build the local SDK before installing a generated UI: npm ci --prefix "$VESTY_SOURCE" and npm run build --prefix "$VESTY_SOURCE". With no template option, new defaults to React; explicit --kind and --ui override template defaults.

Templates include native gain and instrument examples plus vanilla, React, Vue, and Svelte Web UI starters. Generated UI controls initialize from current ready.paramValues and subscribe to confirmed changes.

Development and build

Bash
vesty dev --config vesty.tomlvesty build --config vesty.toml

Keep ordinary Rust and npm checks in the loop as well. The CLI does not replace compiler, linter, or unit-test output.

Protocol and manifests

Bash
vesty export-types --out target/vesty-protocolvesty export-types --out target/vesty-protocol --checkvesty param-manifest \  --specs params.specs.json \  --out vesty-parameters.json \  --check

Use --check in CI to detect generated-file drift.

Diagnostics

Bash
vesty doctor --format jsonvesty smoke-host --out target/smoke-host.json

smoke-host checks repository configuration, sidecars, and optional bridge/meter traces. It is a headless self-check, not a DAW or validator run.