Getting missing script: start error in npm

Question

I get this error when I run npm start.

npm ERR! Missing script: "start"  
npm ERR! Did you mean one of these?
npm ERR!     npm star # Mark your favorite packages
npm ERR!     npm stars # View packages marked as favorites
npm ERR! To see a list of scripts, run:
npm ERR!   npm run
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\USER\AppData\Local\npm-cache\_logs\2022-04-28T13_04_19_260Z-debug.log

it is probably something like npm run start. otherwise check your package.json file, under the property script it shows you the available scripts for the project — Gijs Beijer
– Gijs Beijer, Commented Apr 28, 2022 at 13:22
Edit your question to include your package.json and read the docs for npm start where it says you need a start script like "scripts": { "start": "node foo.js" } — Wyck
– Wyck, Commented Apr 28, 2022 at 13:28

RobC · Accepted Answer · 2022-04-28 17:45:53Z

1

package.json has various sections, scripts is one of them, which allows you to write npm scripts which we can run using npm run <script-name>. The error you're getting is because your start script is missing in that section.

For a node app, your package.json file should look similar to this.

{
    "name": "server",
    "version": "1.0.0",
    "description": "",
    "main": "app.js",
    "scripts": {
        "start": "node app.js",
        "test": "echo \"Error: no test specified\" && exit 1"
    },
    "keywords": [],
    "author": "",
    "license": "ISC",
    "dependencies": {
        "body-parser": "^1.20.0",
        "cors": "^2.8.5",
        "express": "^4.17.3"
    }
}

In the above code, focus on the scripts section. The following line is missing in your package.json file.

"scripts": {
    "start": "node app.js",
},

Add this line and you're good to go.

edited Apr 28, 2022 at 17:45

RobC

25.3k21 gold badges87 silver badges88 bronze badges

answered Apr 28, 2022 at 13:34

Amit

1,1832 gold badges11 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Gep Sher · Accepted Answer · 2022-11-24 10:54:47Z

1

Option_1: Control inside file "package.json":

"scripts": {            
    "start": "what command is here?",                  
    },

Option_2: Control Terminal (folder) where you write command OR open the responding terminal for your project: right-click on the project name -> "Open in integrated Terminal"

answered Nov 24, 2022 at 10:54

Gep Sher

274 bronze badges

Comments

SanderM · Accepted Answer · 2023-03-17 20:17:22Z

0

I had the same error and I had the "start" script and everything should have worked, but it didn't. What actually helped me eventually was just saving the changes, ctrl+s. That's it, I just had to save changes and then it worked.

answered Mar 17, 2023 at 20:17

SanderM

1

Comments

Shambi Broome · Accepted Answer · 2023-08-15 01:18:15Z

0

Just happened to me and my package.json was correct. My fix was that I had something running on port 3000 & didn't realize it.

I used the debugger on the "start" code line under "Scripts" in the package.json
It told me something was already running on port 3000 then asked " Would you like to run the app on another port instead? (Y/N)
I click my "Y" key - the debugger compiled and opened my app on port 3001
Form I was trying to render loaded perfectly

answered Aug 15, 2023 at 1:18

Shambi Broome

11 bronze badge

Comments

Aericki Ferreira · Accepted Answer · 2023-10-16 17:29:02Z

0

Do you have put node on Firewall settings public an private network

answered Oct 16, 2023 at 17:29

Aericki Ferreira

1

1 Comment

Community Over a year ago

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.

Naing Lin Aung · Accepted Answer · 2024-03-11 10:24:19Z

0

if you are facing this issue for the react after creating the react app then always check for the folder are you in is correct or not .....? run cd "project name" and try npm start command again

edited Mar 11, 2024 at 10:24

Naing Lin Aung

3,4404 gold badges34 silver badges51 bronze badges

answered Mar 10, 2024 at 11:02

Yash Katkar

1

Comments

Rahul adya · Accepted Answer · 2024-06-21 15:08:59Z

0

there will be an option to debug in the code above the scripts . just click on the debug option and click on start or build or whatever fuctionality you want to do.....

answered Jun 21, 2024 at 15:08

Rahul adya

1

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Mohana Sundaram S · Accepted Answer · 2022-04-28 13:24:38Z

-1

You have to put what command you need npm to run when you give npm start.

You have to write node index.js in scripts.start in your package.json file

answered Apr 28, 2022 at 13:24

Mohana Sundaram S

1804 bronze badges

Collectives™ on Stack Overflow

Getting missing script: start error in npm

8 Answers 8

Comments

Comments

Comments

Comments

1 Comment

Comments

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

Comments

Comments

Comments

Comments

1 Comment

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related