npm ERR! Missing script: "start"
The script name you ran isn’t defined in package.json "scripts".
Exact message you may see
Missing script:npm ERR! missing script
Seen on:
npm
Meaning
Typos (npm run dev vs serve), running in the wrong folder, or projects that use a different command.
Common causes
- Script not defined
- Wrong directory
- Typo in the script name
⚡ Quick fix
- List scripts: npm run
- Add the script to package.json
- cd into the right project
Detailed fix by platform
npm
npm run # lists available scripts
How to diagnose
- Scripts — Which ones exist?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026