v1.9.3 — a --quiet flag for parallel runs

Jul 28, 2026 | 2 min read

The new --quiet / -q flag hides the header banner and the Local server / Network / LiveReload lines, so several Poops instances running side by side don't bury the compile logs under three copies of the same address block.

Added

--quiet / -q hides the banner. Running one Poops instance, the header and the address block are the useful part of startup. Running several at once — a library build in the repo root and its docs site under site/, each with its own poops.json — they stop being useful: three headers, three terminal bells, and two Local server blocks whose ports you already know, scrolling past before the first compile line lands.
```
poops -q & poops -q -c site/poops.json
```
What -q removes is exactly the startup furniture:
```
💩 Poops — v1.9.3         ← header, and its terminal bell
-----------------
🏠 Local server: …        ← the address block
🛜  Network     : …
🔃 LiveReload  : …
```
Everything else prints as before — [style] Compiled:, [markup] Compiled:, warnings, errors, the non-zero exit on a failed build. The flag is deliberately not a log level: in a parallel run the compile lines are the one thing you're watching, and the tags already tell you which stage spoke.

It composes with the other flags, so it fits a CI build the same way it fits a split terminal:
```
poops --build --quiet --base-url /blog
```
Ports are still resolved and still auto-incremented when one is taken — -q only stops them being announced. If you need to see which port an instance landed on, drop the flag for that one instance and keep it on the rest.

Fixed

justMinified no longer throws ENOENT on watch rebuilds. The post-minify step always deleted the unminified output, but watch rebuilds hand the compiled code to the minifier in memory — the file was never on disk, and every rebuild of a justMinified entry printed an unlink ENOENT stack trace. Harmless but loud. The delete now only runs when the file actually exists.