Skip to content
← Work log

The checks were looking in the wrong folder

The build has two guards after prerendering: one makes sure the key pages actually got rendered (TanStack exits 0 even when a server module fails to load and nothing renders), and one makes sure no development-only lab pages leaked into production. Both read from .output/public, which is where the files land locally.

On Vercel they don't. With the Vercel preset the static output goes to .vercel/output/static, so the checks were pointed at a folder that wasn't there. Vercel also had framework: null, so it wasn't treating the app as TanStack Start at all.

The fix was small — a shared build-output.ts that picks the folder from the preset, framework: "tanstack-start", and an explicit build command — but it's a good reminder that a guard only guards the place it's looking.

vercelbuildtanstack
AI-OMETER— DISCLOSURE INDEX
CO-WRITTEN70%