Fix · Node, npm and build

npm ci fails: package.json and package-lock.json are not in sync

What you may see

The build on the host fails at install with a lock file message
I edited package.json by hand

Most likely cause

package.json lists packages that package-lock.json does not know (or the reverse), because one of them was changed without the other.

Check first (about two minutes)

Run git status: is package-lock.json changed but not committed?

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
npm ci fails: package.json and package-lock.json are not in sync

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
package.json lists packages that package-lock.json does not know (or the reverse), because one of them was changed without the other.

DO THESE STEPS, IN THIS ORDER
1. Run npm install locally to update the lock file, then show me git diff --stat for the two files.
2. Check that only expected packages changed, commit BOTH files together, and push.
3. Confirm the host uses the same package manager as the lock file.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- npm ci passes locally on a clean checkout and on the host.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not delete the lock file to "fix" it.
- 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 npm install locally to update the lock file, then show me git diff --stat for the two files.
Check that only expected packages changed, commit BOTH files together, and push.
Confirm the host uses the same package manager as the lock file.

Do not do this

Do not commit only one of the two files.
Do not delete the lock file to "fix" it.

Try another entry