New Lovable app shows 404 on every page on Vercel

Axonscape — Wed, 28 Oct 2026 09:40:53 +0000

Lovable projects made since May 2026 use TanStack Start, which renders pages on a server. Built for Cloudflare Workers, they 404 on Vercel until they're built with Nitro.

What you see

Every page on Vercel, the home page included, shows 404 NOT_FOUND, or the deploy has no pages at all. The vercel.json rewrite that fixes older Lovable apps doesn't help, and can make it worse.

Why it happens

Since 13 May 2026, Lovable builds apps with TanStack Start, which makes each page on a server rather than in the browser. Its build says where that server runs. Set up for Cloudflare Workers (@cloudflare/vite-plugin and a wrangler.jsonc), it produces something Vercel can't run.

How to fix it

Check package.json for @tanstack/react-start. If it's there, this page is about your app.
Build with Nitro, which Vercel detects and runs: npm i nitro, then add nitro() from "nitro/vite" to the plugins in vite.config.ts, beside tanstackStart() and viteReact().
Don't write a Nitro preset in, so Vercel is detected by itself.
Remove any vercel.json rewrite to /index.html: a server-rendered app has no index.html to send pages to.
Deploying to Cloudflare Workers with wrangler works as the app is.

Or ask your AI tool to fix it

Paste this into Lovable, Bolt, v0, Replit or Cursor:

This TanStack Start app needs to deploy to Vercel, and it's set up to run on Cloudflare Workers. Make its build use Nitro: install nitro and add nitro() from "nitro/vite" to the Vite plugins, beside tanstackStart() and viteReact(). Don't hard-code a Nitro preset, and remove any vercel.json rewrite to /index.html. Keep the app working in Lovable's own preview: only use Nitro when process.env.VERCEL is set. Don't change what the app does.

The full page, with the request ready to copy, is at launchpad.axonscape.com/fix/lovable-tanstack-start-404-on-vercel. I work on Launchpad by Axonscape, which runs a free launch check for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.

Pages show 404 when refreshed or opened directly

Axonscape — Wed, 28 Oct 2026 00:13:45 +0000

Your Lovable or Bolt app works from the home page, but /dashboard shows 404 on Vercel or Netlify when you refresh it or open a link to it. One small file fixes it.

What you see

The home page loads. Clicking around works. But refresh /dashboard, or open a link someone shared to it, and the host answers 404 NOT_FOUND.

Why it happens

The app is a single-page app: its pages exist only in the browser, drawn by a router (React Router, Wouter). The host is asked for a file called /dashboard, has none, and says so. Inside Lovable or Bolt, their hosting sends every address to the app for you.

How to fix it

On Vercel, add a file named vercel.json at the top of the repository with: { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }
On Netlify, add public/_redirects with the line: /* /index.html 200
On Cloudflare Pages, you need nothing: it sends unknown addresses to the app by itself.
Commit, push, and open a deep link again.

Or ask your AI tool to fix it

Paste this into Lovable, Bolt, v0, Replit or Cursor:

My app shows 404 when a page other than the home page is refreshed or opened directly on Vercel. Add a vercel.json at the root of the repository that rewrites every path to /index.html, so the router handles it. Don't change anything else.

The full page, with the request ready to copy, is at launchpad.axonscape.com/fix/page-404-on-refresh. I work on Launchpad by Axonscape, which runs a free launch check for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.

DEV Community: Axonscape

New Lovable app shows 404 on every page on Vercel

What you see

Why it happens

How to fix it

Or ask your AI tool to fix it

Pages show 404 when refreshed or opened directly

What you see

Why it happens

How to fix it

Or ask your AI tool to fix it