bach preview shows the window, bach build writes the setup file and bach inspect shows what a finished setup file contains. This page explains how they fit together.
Preview the window
--uninstall to see the removal window, --theme to force system, light or dark, and --lang to see another language. Preview needs Windows; on macOS and Linux use bach check.
Build the setup file
dist/{name}-Setup-{version}.exe. Change that with installer.output ({name}, {version} and {id} are filled in) or once with --out.
installer.compression sets the default: best makes the smallest file, normal and fast build quicker. Unpacking is fast either way.
On macOS and Linux the setup file keeps Bach’s icon. Build on Windows to apply
app.icon.[updates] section that has a download_url, the build also writes latest.json next to the setup file. bach build exits with a non-zero code and a readable message on any problem, so it works in a pipeline as it is.
Inspect a setup file
bach inspect shows what a setup file, or an installed uninstall.exe, carries: the app id, publisher, program, number and size of files, install folder, options, components, link schemes, file types, languages, license, texts, requirements, shortcuts, update feed and data folders. It reads signed setup files too.
Try the real thing
Running the built setup file is a real install on the machine you run it on. Use it deliberately, then remove the app again from Settings › Apps. For tests, install silently and remove silently:0 means done, 1 failed (the reason is printed in a terminal) and 2 a flag mistake. Every run also writes a log to %TEMP%\<app id>-setup.log. See Silent installs.
Next steps
Sign your setup file
Do it after bach build, never before.
Command reference
Every command and flag.