Deploy a React and Vite site to production
Build a React/Vite site, check its static output, publish with the Shipvela CLI, and troubleshoot missing assets or broken deep links.
Read guideChoose the job you need to finish. Each guide covers the setup, the expected result and what to check when a step fails.
Build a React/Vite site, check its static output, publish with the Shipvela CLI, and troubleshoot missing assets or broken deep links.
Read guideLet Claude Code build and publish a static site through the existing Shipvela CLI, with scoped access and a verifiable deployment result.
Read guideImport an npm project from GitHub, verify the branch and pushed commit, trigger a Shipvela deployment, and inspect the exact build job.
Read guideConnect your domain to a published Shipvela project, copy the issued DNS records, verify HTTPS, and recover from certificate or DNS errors.
Read guideSet public Vite build variables for local uploads or GitHub builds, rebuild when values change, and keep private credentials out of browser bundles.
Read guideDiagnose React Router refresh 404s with a tested Vite example. Check SPA routing, asset responses, base paths and the difference between server and app errors.
Read guideTrace Vite dynamic-import failures with a two-release local reproduction. Distinguish stale chunks, missing assets, HTML fallbacks and blocked requests.
Read guideBuild and inspect a Next.js static export, test nested routes and recognize server-only features. Understand Shipvela’s prebuilt upload and paid Next 12–15 SSR limits.
Read guideFind the first failing stage of a Vite deployment. Reproduce npm, entry-file and import errors, check output settings, then verify the corrected artifact.
Read guideUse an evidence-based launch checklist for a static React/Vite site: build, routes, assets, forms, mobile, search metadata, domain, access and release recovery.
Read guide