The projects and tasks of a MonoSmith
workspace, in the side bar.
Projects view: apps, libs and packages, each with its language, and a
dot on those the changes affect. Under a project, its tasks.
Run a task with the play button on it. The output panel shows the exact
command, then the task output as it arrives; each task shows how it ended
(passed, failed, cached, skipped). Cancel stops the run and its processes.
Status bar: the smith that is running and how many projects are affected.
The extension does not carry smith. It runs the one your team installed, so the
editor, the terminal and CI give the same result. It looks for it in this order:
the monosmith.path setting
the workspace's own install: node_modules/.bin/smith (npm i -D monosmith)
or .smith/bin/smith
smith on the PATH
It talks to smith serve (JSON-RPC over stdin and stdout, no network port) and
works with any smith whose protocol it knows; see
Serve and the event stream.
Generated by smith: smith run package -p vscode packs it into a .vsix in
dist/drop, and a release publishes it to the Marketplace with the token in
VSCE_PAT.
