Presolve/Docs
Menu

These docs cover 0.2.0-beta.26. Each guide distinguishes supported beta behavior, explicit deployment boundaries, and retained 0.1 compatibility material.

Browse documentationAll guides
DocumentationChoose a guide or reference

Ship · confidence workflow

Test and verify

Presolve confidence spans authored source, compiler products, generated HTML, browser lifecycle, and deployment inventory. A component snapshot alone cannot prove a compiler-owned capability.

1. Check authored semantics

pnpm check

Run checks after changes to components, state, actions, computed getters, effects, structural rendering, slots, Context, forms, resources, routes, or capabilities. Fix the first compiler diagnostic before interpreting follow-on failures.

2. Build and inspect the publication

pnpm buildpnpm exec presolve explain app/routes/index.tsx
✓

Document Route HTML contains the correct language, title, metadata, content-addressed stylesheet link, and landmarks.

✓

Assets The referenced app.<sha256>.css, compatibility app.css, and every public/ file exist at their public paths.

✓

Artifacts Runtime, resume, route, and deployment products share one build identity and inventory.

✓

Meaning presolve explain reports expected components, state, actions, and generated memberships without decorator warnings.

3. Prove browser lifecycles

Exercise the exact capability at narrow and wide viewports, from a cold page and a compatible resumed state where applicable.

InteractionEvents call the exact action; bindings receive the expected batch result.
StructureConditional and keyed hosts retain/reorder identity and remove stale events.
EffectsAffected effects schedule after updates and cleanup in child-first order.
ResumeValid snapshots restore exact owners; malformed data takes one clean cold path.
Forms/resourcesValidation, serialization, resource states, cancellation, and restoration follow their declared codecs.
AccessibilityKeyboard focus, landmarks, labels, zoom, reduced motion, and mobile navigation remain usable.

4. Prepare deployment without upload

pnpm deploy:prepare

The provider projection validates the matching immutable inventory and rejects server capabilities the adapter cannot execute. Inspect .presolve/cloudflare/, but do not commit generated projection or dist/.

5. Deploy and smoke test the public origin

pnpm deploy

Verify / remains the root URL, CSS persists through navigation and interaction, public assets return successfully, code samples remain within the viewport, and the live action works on the deployed build.

Report a useful issue

  • All Presolve package versions and the installed TypeScript version.
  • Operating system and native CLI package.
  • A minimal authored-source reproduction.
  • The exact diagnostic code, message, and source span.
  • The output of pnpm exec presolve doctor and relevant explain facts.
  • The affected generated artifact or precise browser observation.
Next guideProduction builds →ReferenceDiagnostics →