build: switch from npm to yarn

integration/README.md

@@ -24,11 +24,8 @@ Note that the `package.json` file uses a special `file://../../dist` scheme
 to reference the Angular packages, so that the locally-built Angular
 is installed into the test app.
 
-Also, beware of floating (non-shrinkwrapped) dependencies. If in doubt
-you can install the package directly from `file:../../node_modules`. For example,
-this is useful for protractor, which has a slow post-install step
-(`webdriver-manager update`) that can be skipped when the package from
-Angular's `node_modules` is installed.
+Also, beware of floating (non-locked) dependencies. If in doubt
+you can install the package directly from `file:../../node_modules`.
 
 ## Running integration tests
 

integration/hello_world__closure/package.json

@@ -23,6 +23,7 @@
     "protractor": "file:../../node_modules/protractor"
   },
   "scripts": {
+    "postinstall": "webdriver-manager update --gecko false",
     "closure": "java -jar node_modules/google-closure-compiler/compiler.jar --flagfile closure.conf",
     "test": "ngc && yarn run closure && concurrently \"yarn run serve\" \"yarn run protractor\" --kill-others --success first",
     "serve": "lite-server -c e2e/browser.config.json",

integration/hello_world__systemjs_umd/package.json

@@ -4,6 +4,7 @@
   "version": "0.0.0",
   "license": "MIT",
   "scripts": {
+    "postinstall": "webdriver-manager update --gecko false",
     "test": "concurrently \"npm run serve\" \"npm run protractor\" --kill-others --success first",
     "serve": "lite-server -c bs-config.e2e.json",
     "preprotractor": "tsc -p e2e",