Skip to content

hiiu serve

Serve a built bundle on a loopback port, offline, with no account and no network.

hiiu serve <bundle>

Extracts a .tgz bundle and serves it as static files on a loopback port. Nothing reaches the network, and no account is involved.

Arguments and flags

<bundle> A .tgz bundle path. Required
--port <number> The loopback port to bind. Omit it and hiiu picks a free one

Every global flag applies.

Where a bundle comes from today

Why it still exists

The bundle format and the serving path are the parts of the sharing story that were real, and keeping them means the work that proved them stays proved: that a built bundle carries the world's serving runtime, that the service worker registers at the served root with the right content type, and that the handlers and the world travel alongside it.

When sharing comes back it comes back to a format that already works and a server that already serves it.

What it does not prove on its own

A bundle served here renders, and its service worker registers. Whether an intercepted API call is answered from the store needs a real browser, because no service worker runs inside the test harness. Opening the printed URL is the test.

Extraction is content addressed

Bundles are named by base id, so serving the same bundle twice reuses the same extracted tree rather than unpacking it again. The extraction is staged and renamed, so two runs at once cannot race each other into a half written directory.

Exit codes

Code When
0 The server started
2 --port was not a whole number between 1 and 65535
3 No bundle at that path