@valerypopoff/rivet2-cli

Command-line tools for running and serving Rivet 2 projects through the Node runtime.

Usage

npx @valerypopoff/rivet2-cli --help
npx @valerypopoff/rivet2-cli list my-project.rivet-project
npx @valerypopoff/rivet2-cli inspect my-project.rivet-project
npx @valerypopoff/rivet2-cli doctor my-project.rivet-project
npx @valerypopoff/rivet2-cli run my-project.rivet-project
npx @valerypopoff/rivet2-cli evaluations run --project my-project.rivet-project --suite-file evaluation.json
npx @valerypopoff/rivet2-cli serve my-project.rivet-project --port 8080
npx @valerypopoff/rivet2-cli serve-app my-project.rivet-project "My web app"
npx @valerypopoff/rivet2-cli completion

The Evaluations command consumes a suite + dataset bundle exported from Rivet's application-local Evaluations workspace. The project supplies its target and evaluator graphs; the bundle does not contain graph definitions, baselines, run history, or recordings. Use --benchmark for measurement without quality checks, --json for a complete EvaluationRun, or --junit for CI.

The CLI package exposes the rivet binary when installed globally:

npm install -g @valerypopoff/rivet2-cli
rivet --help

Development

yarn workspace @valerypopoff/rivet2-cli run build
yarn workspace @valerypopoff/rivet2-cli run test
yarn workspace @valerypopoff/rivet2-cli run lint
yarn workspace @valerypopoff/rivet2-cli run smoke:package
yarn workspace @valerypopoff/rivet2-cli run smoke:docker
yarn workspace @valerypopoff/rivet2-cli run verify

smoke:package is part of verify and checks the generated package contents, direct built binary, and installed rivet command. smoke:docker is opt-in because it requires a local Docker daemon; it removes its temporary smoke image after the check.

Publish the public packages through the repo-root publish script or GitHub workflow, not by running npm publish inside packages/cli.

See the root README, package docs, and public CLI docs under packages/docs/docs/cli.md.