hiiu dev
Run the app's own dev server inside a base, on loopback, with the interception layer injected and hot reload intact.
hiiu dev [path]Resolves the base exactly as build
does, then runs the app's own dev script inside it on a loopback port.
Hot reload keeps working, because hiiu wraps the app's toolchain rather than replacing it. That is the whole reason the inner loop stays fast enough to prototype in.
Arguments and flags
[path] |
The repo or app directory to run. Default . |
--decisions <file> |
The confirmed decisions document to build against |
--port <number> |
The loopback port to bind |
--no-open |
Do not open a browser tab |
Every global flag also applies.
Readiness is an HTTP response
Never a scraped log line. hiiu polls the port until the server answers, so readiness does not break when a framework changes its startup banner.
Under --json, that readiness record is the one document on stdout and
everything after it goes to stderr, so a script can wait for the port and then
leave the process running.
Shutting down
SIGTERM kills the child's process group and exits 0. Killing the dev server
alone would leave whatever it spawned behind.
Exit codes
| Code | When |
|---|---|
0 |
Ran, and shut down cleanly |
3 |
Dirty tree, or not a supported app |
4 |
The app failed to build |
Example
hiiu dev --json --no-open | jq '.url'