Match hosting to the React app’s runtime, build with deliberate environment settings and verify routes, APIs, caching and rollback on the production artifact.
Determine whether the project is a static client app, a static export or a framework app needing server execution. Read its actual build scripts and output configuration. List routes, API dependencies, authentication and any database change in this release. Choose hosting that supports those requirements and record the acceptance checks.
List the configuration needed during build and at runtime. Confirm how the framework exposes values to the browser; Vite’s VITE-prefixed values are bundled into client code. Keep secret credentials in a supported server environment and provide non-secret examples for required settings. Verify the production API origins, base path and authentication callback URLs.
Install from the project’s lockfile using the supported runtime, run the relevant checks and execute the configured production build. Inspect the output directory and any build warnings. For a Vite static app, dist is the default output unless changed; vite preview is a local preview, not a production server. Record the artifact or version being tested.
Serve the production artifact with routing behavior matching the intended host. Test direct nested URLs, refresh, back/forward, missing routes and asset URLs. Complete the core flow with appropriate test accounts or services, including loading, empty, failure and expired-session states. Check keyboard and phone layouts and inspect unexpected browser errors.
Set the documented build command, output directory and required host configuration. Use a preview release to verify HTTPS, redirects, API access and cache behavior before promoting through your normal process. Inspect actual response headers with the browser or HTTP client; use the local header parser only for a pasted response block. Coordinate any data migration and rollback separately.
After release, repeat the critical public routes and application flow against the deployed version. Watch the relevant error and service signals. Keep the previous usable artifact or deployment available and document how rollback interacts with data/schema changes. Download the release record with the tested version, configuration references and unresolved issues.
Loading your checklist…
Vite documents its static build output and local preview workflow. Confirm project overrides rather than assuming every React framework exports the same directory.
VITE-prefixed environment variables are exposed in client code. Treat them as public configuration and keep secret operations on an appropriate server.
Pages publishes file, asset-size and build limits. Check the actual output and current limits when selecting a hosting plan.
Keep these task-specific records with the tested version and review date.
| Record | Include | Verify |
|---|---|---|
| Artifact | Version, runtime, lockfile and build command | Same output tested and released |
| Configuration | Public values and server settings references | No secret copied into client assets |
| Recovery | Previous release and data compatibility | Rollback action is documented and tested where practical |
Development-server success does not cover production base paths, environment substitution or host routing.
A code rollback may require data compatibility; document that before a schema-changing release.