fix(puppeteer): The problem caused by global installed puppeteer was solved by reverting it to dev

Author: mirismaili

.travis.yml

@@ -39,14 +39,15 @@ jobs:
       name: "Build and Release"
       node_js: lts/*
 
-      if: env(BUILD_AND_RELEASE) && type == push && tag !~ ^v\d+\.\d+\.\d+ && branch == master &&
+      if: env(BUILD_AND_RELEASE) == FORCE ||
+        env(BUILD_AND_RELEASE) && type == push && tag !~ ^v\d+\.\d+\.\d+ && branch == master &&
         commit_message =~ /^((feat|fix|refactor|perf|build|revert)\(|test\((?i)[\s\S]*?\b(E2E|END-TO-END|END2END)\b)/ # https://regex101.com/r/XWKT5J/1/
 
       script: >-
         if [[ $E2E_TEST == true || $SEMANTIC_RELEASE == true ]]; then
           npm run build:prod && (
             if [ $E2E_TEST == true ]; then
-              npm i -g puppeteer && npm link puppeteer && npm run test:e2e;
+              npm run test:e2e;
             else
               echo E2E-TEST IS DISABLED;
             fi

jest/e2e/browser.js.flow

@@ -6,9 +6,7 @@
 
 const path = require('path')
 
-// noinspection NpmUsedModulesInstalled
-const Page = require('puppeteer')    // Cannot find module 'puppeteer' => See the note in "./config/setup.js"
-// noinspection NpmUsedModulesInstalled
+const Page = require('puppeteer')
 const Browser = require('puppeteer')
 
 const PORT = require('./config/options.js').listenPort

jest/e2e/config/puppeteer_environment.js

@@ -9,8 +9,7 @@ const path = require('path')
 const os = require('os')
 
 const NodeEnvironment = require('jest-environment-node')
-// noinspection NpmUsedModulesInstalled
-const puppeteer = require('puppeteer')   // Cannot find module 'puppeteer' => See the note in "./setup.js"
+const puppeteer = require('puppeteer')
 
 const DIR = path.join(os.tmpdir(), 'jest_puppeteer_global_setup')
 

jest/e2e/config/setup.js

@@ -9,14 +9,7 @@ const path = require('path')
 const url = require('url')
 const http = require('http')
 
-// Before run `test:e2e` you need to run `npm i -g puppeteer && npm link puppeteer` (as a one-time-action).
-// Why it's not in devDependencies?
-// Regularly we install such packages locally (--save or --save-dev) but exceptionally I suggest installing `puppeteer`
-// globally, because of its extra installation step (node install.js ---> Downloading Chromium r662092 - 140.3 Mb) and
-// because it just required for end-to-end tests.
-
-// noinspection NpmUsedModulesInstalled
-const puppeteer = require('puppeteer') // Error: Cannot find module 'puppeteer' => See above note
+const puppeteer = require('puppeteer')
 
 const mkdirp = require('mkdirp')