Fix · Node, npm and build

TypeScript errors stop the build

What you may see

The build prints Type error and stops
The editor shows red lines but the app seemed to work

Most likely cause

TypeScript checks that data has the shape the code expects; one wrong shape stops the production build even if the page seems to work.

Check first (about two minutes)

Read the FIRST error: it gives a file and line number.
Run npx tsc --noEmit to list all the errors without building.

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 knows Node.js, npm and build tools and explains them 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.

THE PROBLEM
TypeScript errors stop the build

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
TypeScript checks that data has the shape the code expects; one wrong shape stops the production build even if the page seems to work.

DO THESE STEPS, IN THIS ORDER
1. Run npx tsc --noEmit and show me the list. Start with the first error only.
2. Explain what the error means in plain words and fix the real cause (the wrong data shape or a missing check for empty values), not just silence it.
3. Repeat for the next error. After each, re-run npx tsc --noEmit.
4. Finish with npm run build.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- npx tsc --noEmit prints nothing and npm run build passes.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not use "any", @ts-ignore, or turn off strict mode or build error checks to pass.
- 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

Run npx tsc --noEmit and show me the list. Start with the first error only.
Explain what the error means in plain words and fix the real cause (the wrong data shape or a missing check for empty values), not just silence it.
Repeat for the next error. After each, re-run npx tsc --noEmit.
Finish with npm run build.

Do not do this

Do not delete the failing file or feature.
Do not use "any", @ts-ignore, or turn off strict mode or build error checks to pass.

Try another entry