VERCEL ERRORS

Bolt export fails on Vercel: build settings and missing services

Your Bolt app works in the builder but its GitHub export fails on Vercel. Check the exported files, real build script, lockfile and external service configuration.

Bolt export: Vercel build failed

The builder and the deployed checkout differ

Bolt can manage hosting and backend services. Exporting source code to a separate host does not prove those services, secrets and settings moved with it.

Checks in order

  1. Confirm the latest Bolt changes are in the GitHub commit Vercel is building. Inspect package.json and keep the lockfile for its package manager.
  2. Run the exported build script locally from a clean install and read the first failing log line. A generic exit code does not identify the cause.
  3. Set the Vercel Root Directory, framework and output to match the actual project. Only use dist for a build that really emits static files there.
  4. Configure required database and authentication services for the new host. Keep browser-safe configuration separate from server secrets.

Do not hide a failed build with routing changes

An SPA rewrite can solve nested-route refresh failures after a successful static build. It cannot install a missing dependency or repair a server handler.

Verify the exported app

Open a nested route directly, test sign-in and exercise one backend operation. Compare the deployed commit and request logs before asking the builder to rewrite the whole app.

What a DeployDoctor scan can check

A repository scan can flag visible configuration risks. It cannot inspect dashboard settings, private credentials, DNS propagation or live service responses. Confirm the result in the deployed environment.

Sources

Documentation last checked 2026-11-15. Vercel can change its documentation; confirm against the linked pages.