Rename npm script

webpack scripts are meant to “build” assets, so place them under the same namespace

* dev => build:dev
* build => build:prod

3 files changed, 4 insertions, 4 deletions

diff --git a/README.md b/README.md
index 80efdf76..78ff6381 100644
--- a/README.md
+++ b/README.md
@@ -53,7 +53,7 @@ Get started
 2. Enter the directory and type `bin/setup`, which will install npm/bower dependencies and create configs. The setup script is written in Bash, you would need bash as a prerequisite.
 3. Setup the configs, see more below
 4. Setup environment variables which will overwrite the configs
-5. Build front-end bundle by `npm run build` (use `npm run dev` if you are in development)
+5. Build front-end bundle by `npm run build:prod` (use `npm run build:dev` if you are in development)
 6. Run the server as you like (node, forever, pm2)
 
 Upgrade guide
diff --git a/bin/heroku b/bin/heroku
index 12f9cc17..9c06c274 100755
--- a/bin/heroku
+++ b/bin/heroku
@@ -31,5 +31,5 @@ EOF
   cp public/js/config.js.example public/js/config.js
 
   # build app
-  npm run build
+  npm run build:prod
 fi
diff --git a/package.json b/package.json
index eab454ad..4c7cbb1c 100644
--- a/package.json
+++ b/package.json
@@ -5,8 +5,8 @@
   "main": "app.js",
   "license": "MIT",
   "scripts": {
-    "build": "webpack --config webpack.production.js --progress --colors",
-    "dev": "webpack --config webpack.config.js --progress --colors --watch",
+    "build:dev": "webpack --config webpack.config.js --progress --colors --watch",
+    "build:prod": "webpack --config webpack.production.js --progress --colors",
     "assets:install": "bower install",
     "postinstall": "bin/heroku",
     "start": "node app.js"