Fix · Node, npm and build

ESLint errors block the build

What you may see

The build stops on lint messages such as unused variable
It builds locally but fails on the host

Most likely cause

The host runs the style checker as part of the build, and one rule that you do not fail on locally is stricter there.

Check first (about two minutes)

Run npm run lint and read the rule names at the end of each line.

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
ESLint errors block 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
The host runs the style checker as part of the build, and one rule that you do not fail on locally is stricter there.

DO THESE STEPS, IN THIS ORDER
1. Run the lint command and group the messages by rule.
2. Fix real problems (unused code, missing keys, wrong quotes). For a rule that really does not suit the project, ask me before changing the rule.
3. Re-run lint and the build.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- npm run lint ends with no errors and the host build passes.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not switch off lint for the whole 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

Run the lint command and group the messages by rule.
Fix real problems (unused code, missing keys, wrong quotes). For a rule that really does not suit the project, ask me before changing the rule.
Re-run lint and the build.

Do not do this

Do not add disable comments everywhere.
Do not switch off lint for the whole build.

Try another entry