Npm error missing script start

Sign Up for Our Newsletters

Get notified on the latest articles

By checking this box, you confirm that you have read and are agreeing to our terms of use regarding the storage of the data submitted through this form.

If you have worked on JavaScript applications, you have seen and probably used Node.js. There are lots of tools in Node.js, and npm (node package manager) can help you manage them. npm installs the packages you want and provides a terminal interface so you can work with these tools and packages. 

You may get the missing script: start message if you recently updated to the newest version and tried to run npm start on your terminal. Or you may be running a command such as node Filename.js to run your file while not having a script for start. There could be other contributing factors.

Whatever the case, you can follow the steps below to learn how to run npm start without incurring an error message. 

What is the Cause of the npm err! missing script: start Error?

If you type npm start and get the npm err! missing script: start error, there must be a missing line in the script object located in your package.json file. The error also tells us that the missing content is in regards to the start command. 

How to Fix the Error Message

Let’s go over some steps we can take to fix this error. We will go into our project’s package.json file and add a start script to the file so we can use the npm start command.

• First, go into your package.json file by typing npm init in your terminal. You will be taken through the process of creating a package.json file. The utility will ask you a few basics, such as project name and starting file name. I have a file named “App.js” I’m working with, so I typed that in for the “entry point” option. Choose the best options for you, and press Enter to accept the defaults. 

• Now go to the location of the file and open it. The package.json file will be saved in the directory you are currently in inside your terminal. I was in my user directory (the same place where my “App.js” file is) so I found the file there. Then, add a start script in the “scripts” object in your package.json file. This will help to help activate your npm start command.

• Finally, run npm start again. You should be able to run it successfully now!

Conclusion

In this article, you learned how to fix a line in a file so that the npm start command works. As you saw, the error that was thrown at us was pretty descriptive—there was a missing script regarding the start command! 

In the solution we discussed, we went into our package.json file where our scripts live and added a start script. When you get an error, be sure to read the description for clues!

If you want to learn more about npm, check out this article on the best resources to learn npm. Good luck!

After creating a react app using your favorite method and the next method is mostly done by a developer is npm start which spins up a server in your localhost on port 3000 by default unless or until explicitly mentioned. But sometimes this command leads to an npm err! This is what the blog tries to cover and help fix the error.

Introduction?

There are different errors faced while using npm like broken npm installation, no git, no space, etc. In that way, today we are dealing with the npm error encountered when the start command is not triggered.

Reasons for the error?

There can be more than one possible situation that causes this error. These are as listed:

• Not in the correct project directory
• Your `package.json` file doesn’t contain the start script

Incorrect Project Directory

As soon as you create a new react application it creates a new folder in the present directory and all the files of the react application reside there. You are required to jump into the directory as per the name of your project while creating and then run the npm commands.

Missing npm script in package.json

When a react app is initialized it automatically generates a package.json file. It contains a script key that has several other contents like build, test, and eject. Make sure that it contains the start key with the appropriate command to shoot up the react local server.

Overcome the npm encountered error⚒️

There are 2 ways through which we can avoid this error.

• Run the command in an appropriate directory
• Start command present in package.json

Note: These steps assume that you already have a react project initialized.

Run the npm start command in the appropriate directory

After initializing the react app make sure to checkout to the project directory using the command:

cd <project-name>
Code language: Bash (bash)

After shifting to the project directory run the required command:

npm start
Code language: Bash (bash)

This would partly resolve the error, considering that there is a start script present in the package.json file. Even if this doesn’t solve the issue then continue reading to get the solution.

Ensuring the presence of the start script in package.json

The package.json  is the heart of any node project. It contains necessary data about the project which is required before publishing to npm, and also defines functional attributes of a project that npm uses to install dependencies, run scripts, and identify the entry point to our package. Hence make sure that there are no issues in package.json.

This is an example package.json which resolves the issue.

{
  "name": "<project-name>",
  "version": "1.0.0",
  "scripts": {
    "start": "react-scripts start"
  }
}
Code language: JSON / JSON with Comments (json)

But a more robust script would contain almost all required commands ranging from start to eject. Here is an example:

"scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }
Code language: JSON / JSON with Comments (json)

This is the more predominant snippet found even in many production-ready codebases not to the fullest at least they contain all the required ones.

Also, you need to make sure that there are only a single “scripts” present in the pakage.json file. If there are multiple scripts then the latter one is taken into consideration ignoring the previous instances. Here is a quick walkthrough of the same:

{
  "name": "<project-name>",
  "version": "1.0.0",
  <strong>"scripts"</strong>: {
    "start": "react-scripts start"
  }
  <strong>"scripts"</strong>: {
    "dev" : "node dev.js"
  }
}
Code language: JSON / JSON with Comments (json)

The above snippet shows multiple “scripts” present in package.json. If you execute the command:

npm run




  


                       
  



Code language: Bash (bash)

then you could observe that only the latter one is considered. Then if we execute the nom start command without this knowledge then again we would face the same npm err! So to avoid the problem we need to combine the text under both scripts and combine them into a single script. Here is an example:

{
  "name": "<project-name>",
  "version": "1.0.0",
  <strong>"</strong>scripts<strong>"</strong>: {
    "start": "react-scripts start"
    "dev" : "node dev.js"
  }
}
Code language: JSON / JSON with Comments (json)

Conclusion?

This blog addresses one of the initial issues encountered i.e. npm ERR! and serves as a blocker to newbies of React which hinders their learning curve. It covers all the potential reasons for facing the issue with various solutions to overcome the error.

A more comprehensive course is being offered by codedamn named Learn NPM – Node Package Manager complete course. It teaches about npm you from scratch and gives a clear walkthrough of all the package.json file as well which is more prominent in this blog.

Learn programming on codedamn

Codedamn is an interactive coding platform with tons of sweet programming courses that can help you land your first coding job. Here’s how:

• Step 1 — Create a free account
• Step 2 — Browse the structured roadmaps (learning paths), or see all courses.
• Step 3 — Practice coding for free on codedamn playgrounds.
• Step 4 — Upgrade to a Pro membership account to unlock all courses and platforms.

Programming is one of the most in-demand jobs today. Learning to program can change your future. All the best!

Table of contents
• [Solved] npm err! missing script: start 
• Npm ERR! missing script: build;
• Npm ERR! Missing script: «build» [Solved]
• How to fix npm ERR! missing script: start issue
• Npm ERR! Missing script: «start» [Solved]
• [Solved] npm ERR! missing script: start
• How To Fix The missing script: “start” npm Error

[Solved] npm err! missing script: start 

People also askWhat does the NPM error missing script “start” mean?What does the NPM error missing script “start” mean?The npm error missing script: “start” means that npm can’t execute the “start” script from your package.json file. This error happens when you run the npm start or npm run start command from the command line. $ npm run start npm ERR! Missing script: «start» npm ERR! npm ERR!How to fix npm ERR! missing script: start issue — Nathan Sebhastian

"scripts": {
  "start": "react-scripts start",
  "build": "react-scripts build",
  "test": "react-scripts test",
  "eject": "react-scripts eject"
}

"scripts": {
    "start": "node your-script.js"
}

node your-script.js

Using «npm run build» fails with «npm ERR! missing script: build»

You put «npm run build && gh-pages -d build» in your deploy script, but you need to tell npm what to do when npm run build is being run. Configure build to whatever …

C:Usersanai_> npm run build
npm ERR! missing script: build

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli   'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose config Skipping project config: C:Usersanai_/.npmrc. (matches userconfig)
5 verbose stack Error: missing script: build
5 verbose stack     at run (C:Program Filesnodejsnode_modulesnpmlibrun-script.js:151:19)
5 verbose stack     at C:Program Filesnodejsnode_modulesnpmlibrun-script.js:61:5
5 verbose stack     at C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:115:5
5 verbose stack     at C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:402:5
5 verbose stack     at checkBinReferences_ (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:357:45)
5 verbose stack     at final (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:400:3)
5 verbose stack     at then (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:160:5)
5 verbose stack     at ReadFileContext.<anonymous> (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:332:20)
5 verbose stack     at ReadFileContext.callback (C:Program Filesnodejsnode_modulesnpmnode_modulesgraceful-fsgraceful-fs.js:78:16)
5 verbose stack     at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:437:13)
6 verbose cwd C:Usersanai_
7 verbose Windows_NT 10.0.15063
8 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "build"
9 verbose node v9.1.0
10 verbose npm  v5.5.1
11 error missing script: build
12 verbose exit [ 1, true ]

{
  "name": "es6",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "build": "webpack"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "webpack": "^3.8.1"
  }

}

module.exports = {
  entry: ['./app/index.js'],
  output: {
    path: './build',
    filename: 'bundle.js'

  }
}

"scripts": {
    "dev": "webpack --config=Scripts/config/webpack.dev.js --watch",
    "build": "webpack --config=Scripts/config/webpack.prod.js",
    "test": "echo "Error: no test specified" && exit 1"
  },

module.exports = {
    entry: ['./app/index.js'],
    output: {
        path: __dirname + '/build',
        filename: 'bundle.js'
    }
}

Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.output.path: The provided value "./build" is not an absolute path!
    -> The output directory as **absolute path** (required).

ERROR in multi ./app/index.js
Module not found: Error: Can't resolve './app/index.js' in '/tmp/es6'
@ multi ./app/index.js

> [email protected] build /tmp/es6
> webpack

Hash: 0578ec98b09c215702c6
Version: webpack 3.12.0
Time: 34ms
    Asset     Size  Chunks             Chunk Names
bundle.js  2.59 kB       0  [emitted]  main
[0] multi ./app/index.js 28 bytes {0} [built]
[1] ./app/index.js 0 bytes {0} [built]

"scripts": {
      "test": "echo "Error: no test specified" && exit 1",
      "watch": "webpack --watch",
      "build": "webpack"
    },

 "scripts": {
    "test": "echo "Error: no test specified" && exit 1",
    "watch": "ts-node-dev --respawn src/Union.ts",
    "serve": "ts-node-dev src/function.ts",
    "build": "tsc"
  },

Npm ERR! missing script: build;

«start»: «npm run lint && npm run build && cd server && npm install && node server.js It was trying to find a script named ‘build;’ with the semi colon, so change it to && …

> eslint --quiet ./simple/js/*.js

npm ERR! missing script: build;
npm ERR!
npm ERR! Did you mean this?
npm ERR!     build

npm ERR! A complete log of this run can be found in:
npm ERR!     C:UsersjgulleAppDataRoamingnpm-cache_logs2020-08-18T08_34_05_215Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm run lint && (npm run build; cd server; npm install; node 
server.js)`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.       

npm ERR! A complete log of this run can be found in:

{
  "name": "encrypt-decrypt-demo",
  "version": "1.0.3",
  "description": "Simple example to encrypt and decrypt files in the TDF spec using Virtru hosted KAS and EAS.",
  "scripts": {
    "build": ".simple/scripts/build.sh",
    "lint": "eslint --quiet ./simple/js/*.js",
    "start": "npm run lint && (npm run build; cd server; npm install; node server.js)",
    "watch": "nodemon --watch ./simple/js --ignore ./simple/js/build --exec 'npm run start'",
    "audit": "audit-ci --config .audit-ci.json"
  },
  "dependencies": {
    "browserify": "16.2.3",
    "moment": "2.24.0"
  },
  "devDependencies": {
    "audit-ci": "^2.3.0",
    "eslint": "^6.2.1",
    "eslint-config-airbnb-base": "^14.0.0",
    "eslint-plugin-import": "^2.18.2",
    "nodemon": "^1.19.1",
    "webpack-cli": "^3.3.6"
  }
}

cleanup(){
    if [ -f ./simple/js/build/demo-utils.js ]; then 
        rm ./simple/js/build/demo-utils.js; 
    fi
}

build(){
    browserify ./simple/js/browserify.js -o ./simple/js/build/demo-utils.js
}

cleanup && build

"start": "npm run lint && npm run build && cd server && npm install && node server.js

Npm ERR! Missing script: «build» [Solved]

To solve the npm ERR! Missing script: «build» error, make sure to add a build command to the scripts object in your package.json file and open your shell or IDE in the root …

Copied!npm ERR! Missing script: "build"
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

Copied!{
  "scripts": {
    "build": "webpack --config webpack.config.js"
  }
}

Copied!npm init -y

Copied!{
  "scripts": {
    "build": "webpack --config webpack.config.js"
  }
}

Copied!webpack --config webpack.config.js

How to fix npm ERR! missing script: start issue

As you can see, the terminal output from npm run is different. The start script is now available. Missing start script because of create-react-app. The missing script start …

$ npm run start
npm ERR! Missing script: "start"
npm ERR!
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!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run
...

{
  "name": "v-app",
  "version": "1.0.0",
  "scripts": {
    "start": "node index.js"
  }
}

{
  "name": "v-app",
  "version": "1.0.0",
  "scripts": {
    "start": "node index.js"
  },
  "scripts": {
    "dev": "gulp"
  }
}

$ npm run
Scripts available in [email protected] via `npm run-script`:
  dev
    gulp

{
  "name": "v-app",
  "version": "1.0.0",
  "scripts": {
    "start": "node index.js",
    "dev": "gulp"
  }
}

$ npm run
Lifecycle scripts included in [email protected]:
  start
    node index.js

available via `npm run-script`:
  dev
    gulp

create-react-app my-app

# 👇 remove the globally installed package
npm uninstall -g create-react-app

# 👇 clear npx cache to ensure you use the latest cra version
npx clear-npx-cache

# 👇 run create-react-app with npx
npx create-react-app my-app

{
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
}

Npm ERR! Missing script: «start» [Solved]

To solve the Missing script: «start» error, make sure to add a start command to the scripts object in your package.json file and open your shell or IDE in the root directory of …

Copied!npm ERR! Missing script: "start"
npm ERR!
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!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

Copied!{
  "scripts": {
    "start": "node index.js"
  }
}

Copied!npm init -y

Copied!{
  "scripts": {
    "start": "node index.js",
  }
}

Copied!node index.js

Copied!# 👇️ uninstall old version
npm uninstall -g create-react-app

# 👇️ clear your cache
npx clear-npx-cache

# 👇️ to create normal React.js project
npx create-react-app my-app

# 👇️ to create TypeScript React.js project
npx create-react-app my-app --template typescript

Copied!# 👇️ for normal React.js project
npx [email protected] my-app --use-npm

# 👇️ for TypeScript React.js project
npx [email protected] my-app --template typescript --use-npm

[Solved] npm err! missing script: start 

One comment. 24. Shares. How to fix npm err! missing script: start. Solution 1 – Add the Start Scripts in package.json. Solution 2 – Ensure you have server.js or add the main …

"scripts": {
  "start": "react-scripts start",
  "build": "react-scripts build",
  "test": "react-scripts test",
  "eject": "react-scripts eject"
}

"scripts": {
    "start": "node your-script.js"
}

node your-script.js

[Solved] npm ERR! missing script: start

Save my name, email, and website in this browser for the next time I comment.

npm ERR! missing script: start

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

{
  "name": "v-app",
  "version": "1.0.0",
  "scripts": {
    "start": "node index.js"
  },
  "scripts": {
    "dev": "gulp"
  }
}

{
  "name": "v-app",
  "version": "1.0.0",
  "scripts": {
    "start": "node index.js",
    "dev": "gulp"
  }
}

How To Fix The missing script: “start” npm Error

It depends on how you write your project and how you plan to run it. Sometimes, you may only need this simple start command: «scripts»: { «start»: «node app.js» }, After adding …

$ npm run start
npm ERR! Missing script: "start"

  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },

npm ERR! missing script: start

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

$ npm run-script
Lifecycle scripts included in [email protected]:
  start
    react-scripts start
  test
    react-scripts test

Next Lesson PHP Tutorial