How to define scripts for npm command?

Question

I am using npm+webpack to manage a react web application. And I want to define a few command for npm in order to run some webpack command. Below is the two command scripts I defined in package.json file.

"scripts": {
"start": "webpack-dev-server --host 0.0.0.0",
"build": "NODE_ENV=production webpack --config ./webpack.config.js --progress --profile --colors"
},

As you can see, there are two commands 'start' and 'build'. When I run npm start it will run webpack-dev-server --host 0.0.0.0 to launch a web server. But when I run npm build, it doesn't run the configured command and simply returns without any output. I wander how to define a script command for npm to use. Below is my whole package.json file:

{


"name": "demo",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "webpack-dev-server --host 0.0.0.0",
    "build": "NODE_ENV=production webpack --config ./webpack.config.js --progress --profile --colors"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "babel-core": "^6.9.0",
    "babel-loader": "^6.2.4",
    "compression-webpack-plugin": "^0.3.1",
    "css-loader": "^0.23.1",
    "less": "^2.7.1",
    "less-loader": "^2.2.3",
    "npm-install-webpack-plugin": "^3.1.3",
    "style-loader": "^0.13.1",
    "svg-sprite-loader": "0.0.26",
    "webpack": "^1.13.1",
    "webpack-dev-server": "^1.14.1",
    "webpack-shell-plugin": "^0.4.2"
  },
  "dependencies": {
    "actions": "^1.3.0",
    "axios": "^0.12.0",
    "babel-preset-stage-2": "^6.11.0",
    "cdnjs": "^0.3.2",
    "components": "^0.1.0",
    "containers": "0.0.1",
    "extract-text-webpack-plugin": "^1.0.1",
    "features": "^0.1.0",
    "file-loader": "^0.8.5",
    "fo": "^0.1.1",
    "jshint": "^2.9.2",
    "jshint-loader": "^0.8.3",
    "leaflet": "^0.7.7",
    "material-ui": "^0.15.2",
    "moment": "^2.13.0",
    "normalize.css": "^3.0.2",
    "nuka-carousel": "^2.0.0",
    "public": "^0.1.2",
    "query-string": "^4.2.2",
    "react": "^15.1.0",
    "react-addons-css-transition-group": "^15.1.0",
    "react-addons-shallow-compare": "^15.1.0",
    "react-alert": "^1.0.14",
    "react-button": "^1.2.1",
    "react-cookie": "^0.4.7",
    "react-date-picker": "^5.3.9",
    "react-datepicker": "^0.27.0",
    "react-dom": "^15.0.2",
    "react-infinite-calendar": "^1.1.14",
    "react-redux": "^4.4.5",
    "react-router": "^2.4.1",
    "react-router-redux": "^4.0.5",
    "react-select": "^1.0.0-beta13",
    "react-spinkit": "^1.1.8",
    "react-tap-event-plugin": "^1.0.0",
    "react-tappable": "^0.8.1",
    "redux": "^3.5.2",
    "redux-thunk": "^2.1.0",
    "sha1": "^1.1.1",
    "source-map-loader": "^0.1.5",
    "src": "^1.1.2",
    "style": "0.0.3",
    "url-loader": "^0.5.7",
    "utils": "^0.3.1"
  }
}

score 3 · Accepted Answer · 2016-08-10 04:19:14Z

3

You can use npm run-script <script-name> to run arbitrary scripts. In your case, npm run-script build.

From the npm documentation, The npm <script-name> syntax is only supported for a specific number of predetermined scripts such as start.

npm supports the "scripts" property of the package.json script, for the following scripts:

prepublish: Run BEFORE the package is published. (Also run on local npm install without any arguments.)

publish, postpublish: Run AFTER the package is published.

preinstall: Run BEFORE the package is installed

install, postinstall: Run AFTER the package is installed.

preuninstall, uninstall: Run BEFORE the package is uninstalled.

postuninstall: Run AFTER the package is uninstalled.

preversion, version: Run BEFORE bump the package version.

postversion: Run AFTER bump the package version.

pretest, test, posttest: Run by the npm test command.

prestop, stop, poststop: Run by the npm stop command.

prestart, start, poststart: Run by the npm start command.

prerestart, restart, postrestart: Run by the npm restart command. Note: npm restart will run the stop and start scripts if no restart script is provided.

Additionally, arbitrary scripts can be executed by running npm run-script <pkg> <stage>. Pre and post commands with matching names will be run for those as well (e.g. premyscript, myscript, postmyscript).

As well, you can use npm run <script-name> as a shorthand.

edited Aug 10, 2016 at 4:19

answered Aug 10, 2016 at 4:04

user4233921

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

1 Comment

Kyle Delaney Over a year ago

What does it mean for prepublish to run "on local"? As opposed to what?

hackerrdave · Accepted Answer · 2016-08-10 04:03:49Z

0

You can define an npm script just like how you have it here:

"scripts": { "start": "webpack-dev-server --host 0.0.0.0", "build": "NODE_ENV=production webpack --config ./webpack.config.js --progress --profile --colors" },

To run the build command enter: $ npm run build

answered Aug 10, 2016 at 4:03

hackerrdave

6,7362 gold badges27 silver badges29 bronze badges

1 Comment

hackerrdave Over a year ago

also - check out this more detailed blogpost on adding more custom npm run scripts: blog.npmjs.org/post/118810260230/…

harishr · Accepted Answer · 2016-08-10 04:04:57Z

0

you need to use command npm run build

answered Aug 10, 2016 at 4:04

harishr

18.1k9 gold badges84 silver badges131 bronze badges

2 Comments

Joey Yi Zhao Over a year ago

Thanks it works. But why I don't need 'npm run' for start?

user4233921 Over a year ago

@ZhaoYi see what I posted, start is part of the predefined script list that can be run without the run-script or run command.

Collectives™ on Stack Overflow

How to define scripts for npm command?

3 Answers 3

1 Comment

1 Comment

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related