A based web dev workflow; stack-agnostic, hand-coded, 🦀
A CLI daemon that can:
- watch source
- invoke arbitrary build command
- statically serve
- laungh browser
- trigger page reload
- politely report what it's doing
Caution
This software is not yet ready for use
$ conveyorbelt <build command>
A temporary directory serve path is created
and its contents statically served at http://localhost:<available port>/.
A chromium browser is launched with that URL.
On file changes the <build command> is invoked.
The build process receives the serve path via the environment variable SERVE_PATH.
When the build process exits successfully, the page reloads.
Both suffer the same design problem; they watch the same directory that they serve. That results in the browser being instructed to reload on each file change, without regard to whether a build process had completed or merely made its first change. That design also lacks the convenience of automatic build command invocation.
Another difference is that conveyorbelt controls the browser using Chrome DevTools Protocol while the projects mentioned above use a WebSocket and JavaScript that is injected into the served page.