Deploy to Vercel

Vercel works well with exported Lediv projects, with most settings detected automatically.

You do not have to leave Lediv to put a project online. Publish serves it in seconds. This guide is for the other path, hosting the same project somewhere else.

Prepare the project export

Open the Publish panel in the editor and click Download project. Use that ZIP as the deployment source in Vercel.

Choose a Vercel deploy method

Git import in the dashboard

  1. Unzip the exported project.
  2. Push the project to a Git repository.
  3. Create a new Vercel project and import that repository.
  4. Review settings and continue with deploy.

Deploy from local source with Vercel CLI

  1. Unzip the exported project.
  2. Install Vercel CLI if needed.
  3. Run vercel from the project root and follow the prompts.

Vercel usually detects the Vite settings on its own. If it asks, the build command is npm run build and the output directory is dist.

After deployment

Vercel assigns a live URL after the first deployment. Domain setup and environment-specific config can be managed later from Vercel project settings.

For updates, redeploy from new source changes through Git integration or Vercel CLI.

Vercel does not read a _redirects file. Netlify and Cloudflare Pages do, and so does Lediv, so a project that relies on redirects needs them restated in a vercel.json here. The file still travels with your export. It is simply ignored.

Next steps

Publish Back to the export flow from Lediv. Deploy to Netlify Compare with another common deployment option. Deploy to Cloudflare Cloudflare-based deployment steps. Local Development Advanced workflow with local execution.