pack testing under production environment

README.md

@@ -81,7 +81,6 @@ Notice: The published versions have always passed the CI tests. We highly recomm
 #### Docker
 
 [![Docker Pulls](https://img.shields.io/docker/pulls/zixia/wechaty.svg?maxAge=2592000)](https://hub.docker.com/r/zixia/wechaty/) 
-[![Docker Stars](https://img.shields.io/docker/stars/zixia/wechaty.svg?maxAge=2592000)](https://hub.docker.com/r/zixia/wechaty/) 
 [![Docker Layers](https://images.microbadger.com/badges/image/zixia/wechaty.svg)](https://microbadger.com/#/images/zixia/wechaty)
 
 The **best practice** to use Wechaty is running with docker, because it's not only the most easy way to get started, but also protects you from the troubles of dependency problems. 

package.json

@@ -103,6 +103,7 @@
     "state-switch": "^0.6.2",
     "watchdog": "^0.8.1",
     "wechaty-puppet": "^0.2.12",
+    "wechaty-puppet-mock": "^0.2.5",
     "wechaty-puppet-puppeteer": "^0.2.11",
     "wechaty-puppet-wechat4u": "^0.2.15",
     "ws": "^5.2.0",
@@ -160,8 +161,7 @@
     "tslint-config-standard": "^7.0.0",
     "tuling123-client": "^0.0.2",
     "typedoc": "^0.11.1",
-    "typescript": "^2.9.2",
-    "wechaty-puppet-mock": "^0.2.5"
+    "typescript": "^2.9.2"
   },
   "files_comment__whitelist_npm_publish": "http://stackoverflow.com/a/8617868/1123955",
   "files": [

scripts/npm-pack-testing.sh

@@ -11,12 +11,10 @@ cp tests/fixtures/smoke-testing.ts "$TMPDIR"
 
 cd $TMPDIR
 npm init -y
-npm install *-*.*.*.tgz \
+npm install --production \
+  *-*.*.*.tgz \
   @types/node \
-  rxjs \
-  brolog \
-  typescript \
-  wechaty-puppet-mock \
+  typescript
 
 ./node_modules/.bin/tsc \
   --lib esnext \