Ship · deterministic output

Production builds

A production build is a compiler publication, not a generic JavaScript bundle. It is the complete matching inventory required to render, activate, and resume every admitted route.

Run the release gate

pnpm checkpnpm build

check validates TypeScript and compiler-admitted semantics. build atomically publishes the application into dist/.

What gets published

HTML

Complete route documents

Useful markup and document metadata are available before application code executes.

RUNTIME

Exact browser plans

Bindings, events, effects, activation roots, and lazy chunks follow compiler-known boundaries.

RESUME

Versioned restore products

State codecs, identities, anchors, and restore programs remain one matching inventory.

ASSETS

Application publication

Global CSS, public files, route metadata, manifests, and provider-ready inventory ship together.

Inspect meaning, not emitted code

pnpm exec presolve explain app/routes/index.tsx --format json

Use compiler explanations and manifest products to diagnose state, actions, bindings, and artifact decisions. Generated JavaScript is an execution product, not an authoring API.

Protect artifact integrity

Treat dist/ as immutable output.
Never mix files from two builds or upload selected HTML without its matching products.
Do not patch generated runtime files.
Deploy the exact inventory whose build and resume identities passed verification.

Continue to Cloudflare deployment →