Vercel deploy showed Ready but every route returned 500 until an 8-line export fix
A developer deployed a Node app to Vercel and the dashboard reported a successful 'Ready' status, yet every route returned 500 errors with a 100% failure rate. Local tests passed 84 of 84 and the server answered 200 on every route from the developer's machine, so the code itself appeared sound. Comparing the failing server file with a working sibling project revealed the problem: the broken version exported a named builder function and never created a server instance for Vercel's runtime to invoke. The fix created the server, exported it as the default export, and listened on that instance when run directly. After redeployment, live checks confirmed 200 responses on the health and example routes, though the first check briefly still showed the old 500 result while the new deployment rolled out.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in