FsHotWatch.Cli 0.8.0-alpha.13

FsHotWatch.Cli

Command-line tool for the FsHotWatch daemon. It auto-starts the daemon in the background when you run any command, so you don't need to manually manage daemon lifecycle.

Install

dotnet tool install -g FsHotWatch.Cli

Quick start

# Run all checks (scan, build, lint, errors)
fshw check

# Start daemon in foreground (useful for debugging)
fshw start

# Check plugin statuses
fshw status

Commands

Options

Examples

# Run tests for a specific project
fshw test -p MyApp.Tests

# Run only previously-failed tests
fshw test --only-failed

# Show just the lint plugin's status
fshw status lint

# Query a plugin command directly
fshw diagnostics
fshw coverage
fshw warnings

Config validation

.fshw.json is parsed strictly: any parse or validation error aborts startup with exit code 2 and a message naming the offending field. Use fshw config check to validate without starting the daemon (handy for editor integration and CI).

While the daemon is running, any write to .fshw.json causes it to stop cleanly, logging the reason:

• Valid edit: config changed, stopping (restart to apply)
• Invalid edit: config invalid, stopping: <parse error>

Re-invoke the CLI to start a fresh daemon with the new config. There is no hot-reload — symmetric stop-on-any-change avoids the race risks of mid-flight plugin re-registration.

How it works

The CLI computes a deterministic pipe name from your repo root, then communicates with the daemon over named pipes (StreamJsonRpc). If the daemon isn't running or its config has changed, the CLI automatically starts/restarts it in the background.