Measure three build states without mixing them together

A useful build test tells you which wait improved. This lab gives you three observations you can compare later: first run, unchanged run and one visible edit.

Use a disposable checkout of a supported app with Ionify already configured. Keep your normal build command. Check the setup requirements, including the package's Node version and native optional dependencies.

1. Name the starting state

Record the installed Ionify version, Node version, operating system, package lockfile and configuration. For the first run, say whether local engine state or output already exists. Do not call a run cold merely because you opened a new terminal.

Run:

pnpm exec ionify build

Use your shell's elapsed-time facility or an external timer around the complete invocation. State whether the number includes process startup. Do not mix a tool's internal phase timer with an external wall-clock time.

2. Repeat without a change

Keep the local .ionify state and output directory. Run the same command again. Record this as an unchanged build, separately from the first run.

3. Make a visible edit

In an imported component, change a literal label such as “Save” to “Save draft.” Run the command again, serve the production output using your normal static preview setup, and verify that the new label appears. Then make one more unchanged run.

Copy this result template:

Tool and version:
Node / OS / hardware:
Command and timer boundary:
Starting engine/output state:
First run:
Unchanged run:
Edited run:
Next unchanged run:
Correct output checked:
Raw observations / reproduction:

Repeat the sequence, preserve every trial and note background activity. Do not silently discard a slow run.

Ionify aims to reuse valid local work. This test does not establish remote-cache behavior, HMR latency or compatibility with every integration. A single edited file can still require wider work. The result that matters is a shorter wait for the correct app.

If something fails, share a minimal reproduction through Ionify's issue tracker, without secrets or private source.