Lovable deployment · reviewed September 25, 2026
Lovable app on Vercel showing 404? Check the project type first
The right fix depends on whether your project is a current TanStack Start app or an older Vite single-page app. Check its package files before changing Vercel routing.
Check the Lovable framework version
Vercel’s documentation, updated September 22, 2026, says automatic detection requires @lovable.dev/vite-tanstack-config version 2.6.2 or later. This requirement is for zero-configuration detection; a lower version does not by itself prove the app cannot be deployed with another setup.
For the resolved version, copy it from package-lock.json or enter the exact version shown in your lockfile.
This check runs in your browser. Nothing is uploaded or saved. Paste package metadata only, never secrets or environment values.
Browser-based check
Does your Lovable project meet Vercel’s auto-detection requirement?
Check the declared or resolved @lovable.dev/vite-tanstack-config version without connecting any accounts.
Connect Lovable to Vercel
- In Lovable, connect the project to GitHub and wait until the repository shows the latest changes.
- In Vercel, import that GitHub repository. Vercel says it detects the supported TanStack Start setup automatically.
- After the first deployment, open the production URL and test both the home page and a nested route directly.
- If deployment fails, inspect the first specific build error. If the build succeeds but the site returns an error, check the deployed framework version and Vercel runtime logs before changing routing settings.
Lovable’s GitHub integration is a two-way sync: changes in Lovable sync to the linked repository, and pushes to its active branch sync back into Lovable. Once that repository is connected to Vercel, new commits can trigger deployments.
Older Vite SPA: the home page works, but a route refresh gives 404
Vercel’s Vite guide says deep links need a fallback when a project is configured as a client-side single-page app. If that matches your project, create vercel.json in the project root:
{
"$schema": "https://openapi.vercel.sh/vercel.json",
"rewrites": [
{ "source": "/(.*)", "destination": "/index.html" }
]
}Use this only for a Vite SPA where the client router handles the nested paths. Vercel documents this rewrite for Vite SPAs; current Lovable projects use TanStack Start and follow that framework’s setup. If the root URL also returns 404, first check the Vercel project’s root directory, build output and deployed branch.
If Vercel does not detect the framework
- Confirm that the Vercel project points to the repository and branch that Lovable is updating.
- Check the dependency in the committed package manifest and the resolved version in the lockfile.
- If the resolved version is older than 2.6.2, update the dependency and commit both the package manifest and its lockfile.
- Compare any manual Nitro or Vite configuration with the current framework documentation. Avoid copying a configuration written for a different project generation.
Need help with a failed build log? Use the AI app deployment error checker. For the Spanish guide, open publicar Lovable en Vercel.
Choosing a host for a Lovable app? See the Vercel, Hostinger and DigitalOcean comparison.
Official documentation
Independent guide. The version threshold was checked against Vercel’s documentation on September 25, 2026. This checker does not connect to Lovable, GitHub or Vercel.