Keep useful build work after closing the terminal

Description and use

Demonstrates preserving Ionify build artifacts across process restarts, enabling reuse without keeping a terminal open.

Problem

Closing a terminal should not make you lose the opportunity to reuse valid local work.

Outcome

The workflow demonstrates that Ionify preserves local build state across process restarts, allowing a developer to reuse build artifacts without keeping a terminal open.

Workflow

• Run pnpm exec ionify build in a terminal and let it exit, keeping the project's local state.
• Open a new terminal in the same checkout and run pnpm exec ionify build again, preserving .ionify and output directory.
• Edit a component to change a button label from "Save" to "Save draft" and run the same build command in a fresh process, keeping local state.
• Serve the generated output with a static preview server, e.g., python3 -m http.server 4173 --bind 127.0.0.1 --directory dist.
• Open http://127.0.0.1:4173/ and inspect the button text to confirm the new label.
• Record version, checkout, command, state retention, and observed label.

Evidence

Run each invocation to completion in a fresh process; for the second, open a new terminal in the same checkout. Preserve .ionify and the output directory, including workspace-root state in a monorepo.

Source

Use your project’s static preview setup against the generated output, not the dev server. The CLI’s default build output is dist; if your command explicitly selects another directory with --out-dir, serve that directory consistently.

Source

Open http://127.0.0.1:4173/. Inspect #save-button and confirm its visible text is Save draft.

Source