Fix · Node, npm and build

npm says "found N vulnerabilities"

What you may see

After install I see vulnerabilities and a command to fix them

Most likely cause

The packages (or their helpers) have known issues listed in a public database; many are not reachable in your project.

Check first (about two minutes)

Run npm audit and see which are "high" or "critical" and which packages.

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 says "found N vulnerabilities"

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 packages (or their helpers) have known issues listed in a public database; many are not reachable in your project.

DO THESE STEPS, IN THIS ORDER
1. Run npm audit and group the results: runtime packages (used in the live site) versus build-only tools.
2. Fix the safe ones with a normal npm audit fix; list what would need a major upgrade.
3. Never run npm audit fix --force without showing me exactly what it would change.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- npm audit shows fewer or no high issues in runtime packages, and the build and tests pass.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not upgrade to new major versions just to clear the number.
- 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 audit and group the results: runtime packages (used in the live site) versus build-only tools.
Fix the safe ones with a normal npm audit fix; list what would need a major upgrade.
Never run npm audit fix --force without showing me exactly what it would change.

Do not do this

Do not panic about build-only tools.
Do not upgrade to new major versions just to clear the number.

Try another entry