Fix · Vercel and deploying

Vercel build failed

Blocks your workNot checked against the vendor's current screens

What you may see

The deployment shows Error or Build failed in red
It works on my computer but not on Vercel
My site did not update after I pushed

Most likely cause

The build command stops on one error that does not show on your computer, most often a missing variable, a different version, or a type error.

Check first (about two minutes)

Open the failed deployment and its build log; scroll to the FIRST red line, not the last.
Run the same build command (npm run build) on your computer.

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a patient senior engineer who deploys websites on Vercel every day and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
Vercel build failed

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The build command stops on one error that does not show on your computer, most often a missing variable, a different version, or a type error.

DO THESE STEPS, IN THIS ORDER
1. Ask me to paste the first error lines of the build log (no secrets).
2. Run npm run build locally and compare: if it also fails, fix that error first; if it passes, compare Node version and environment variables with the Vercel project settings.
3. Fix only the cause of the first error. Do not "fix" later errors before the first is gone.
4. Push, and read the new build log.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The deployment turns Ready and the production address shows the change.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not turn off type checks or lint rules just to pass the build.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Ask me to paste the first error lines of the build log (no secrets).
Run npm run build locally and compare: if it also fails, fix that error first; if it passes, compare Node version and environment variables with the Vercel project settings.
Fix only the cause of the first error. Do not "fix" later errors before the first is gone.
Push, and read the new build log.

Do not do this

Do not redeploy ten times hoping it changes: read the log.
Do not turn off type checks or lint rules just to pass the build.

Try another entry