Replace npm with yarn

.gitignore

@@ -54,7 +54,6 @@ cli/build
 # Building app binary
 scripts/support
 package-lock.json
-yarn.lock
 binary-url.json
 
 # Allows us to dynamically create eslint rules that override the default for Decaffeinate scripts

.vscode/launch.json

@@ -11,9 +11,8 @@
       "type": "node",
       "request": "launch",
       "name": "test: active",
-      "runtimeExecutable": "npm",
+      "runtimeExecutable": "yarn",
       "runtimeArgs": [
-        "run",
         "test-debug-package"
       ],
       "args": [
@@ -33,9 +32,8 @@
       "request": "launch",
       "name": "dev-debug",
       "port": 5566,
-      "runtimeExecutable": "npm",
+      "runtimeExecutable": "yarn",
       "runtimeArgs": [
-        "run",
         "dev-debug"
       ]
     }

.vscode/tasks.json

@@ -6,19 +6,19 @@
     {
       "label": "decaffeinate-bulk file",
       "type": "shell",
-      "command": "npm run decaffeinate-bulk -- convert --file ${file}",
+      "command": "yarn decaffeinate-bulk convert --file ${file}",
       "problemMatcher": []
     },
     {
       "label": "decaffeinate-bulk multiple files",
       "type": "shell",
-      "command": "npm run decaffeinate-bulk -- convert --file ${file} ${file}",
+      "command": "yarn decaffeinate-bulk convert --file ${file} ${file}",
       "problemMatcher": []
     },
     {
       "label": "decaffeinate-bulk dir",
       "type": "shell",
-      "command": "npm run decaffeinate-bulk -- --dir ${fileDirname} convert",
+      "command": "yarn decaffeinate-bulk --dir ${fileDirname} convert",
       "problemMatcher": []
     }
   ]

.vscode/terminals.json

@@ -6,58 +6,58 @@
       "focus": true,
       "onlySingle": true,
       "execute": true,
-      "command": "npm run cypress:open"
+      "command": "yarn cypress:open"
     },
     {
       "name": "cypress run",
       "focus": true,
       "onlySingle": true,
       "execute": false,
-      "command": "npm run cypress:run -- --project ../project"
+      "command": "yarn cypress:run --project ../project"
     },
     {
       "name": "packages/server test-watch",
       "focus": true,
       "onlySingle": true,
       "execute": false,
       "cwd": "[cwd]/packages/server",
-      "command": "npm run test-watch -- [file]"
+      "command": "yarn test-watch [file]"
     },
     {
       "name": "packages/server test-e2e",
       "focus": true,
       "onlySingle": true,
       "execute": false,
       "cwd": "[cwd]/packages/server",
-      "command": "npm run test-e2e -- --spec [fileBasename]"
+      "command": "yarn test-e2e --spec [fileBasename]"
     },
     {
       "name": "packages/runner watch",
       "focus": true,
       "onlySingle": true,
       "cwd": "[cwd]/packages/runner",
-      "command": "npm run watch"
+      "command": "yarn watch"
     },
     {
       "name": "packages/driver cypress open",
       "focus": true,
       "onlySingle": true,
       "cwd": "[cwd]/packages/driver",
-      "command": "npm run cypress:open"
+      "command": "yarn cypress:open"
     },
     {
       "name": "packages/desktop-gui cypress open",
       "focus": true,
       "onlySingle": true,
       "cwd": "[cwd]/packages/desktop-gui",
-      "command": "npm run cypress:open"
+      "command": "yarn cypress:open"
     },
     {
       "name": "packages/desktop-gui watch",
       "focus": true,
       "onlySingle": true,
       "cwd": "[cwd]/packages/desktop-gui",
-      "command": "npm run watch"
+      "command": "yarn watch"
     }
   ]
 }

DEPLOY.md

@@ -12,11 +12,7 @@ We build the NPM package and binary on all major platforms (Linux, Mac, Windows)
 providers. In order to set the version while building we have to set the environment variable
 with the new version on each CI provider *before starting the build*.
 
-Use the script command below to to do this.
-
-```shell
-npm run set-next-ci-version
-```
+Use script command `yarn set-next-ci-version` to do this.
 
 ## Building
 
@@ -27,7 +23,7 @@ npm run set-next-ci-version
 Building a new NPM package is very quick.
 
 - Increment the version in the root `package.json`
-- `cd cli && npm run build`
+- `yarn build --scope cypress`
 
 The steps above:
 
@@ -48,22 +44,22 @@ First, you need to build, zip and upload the application binary to the Cypress s
 You can use a single command to do all tasks at once:
 
 ```shell
-npm run binary-deploy
+yarn binary-deploy
 ```
 
 Or you can specify each command separately:
 
 ```shell
-npm run binary-build
-npm run binary-zip
-npm run binary-upload
+yarn binary-build
+yarn binary-zip
+yarn binary-upload
 ```
 
 You can pass options to each command to avoid answering questions, for example
 
 ```shell
-npm run binary-deploy -- --platform darwin --version 0.20.0
-npm run binary-upload -- --platform darwin --version 0.20.0 --zip cypress.zip
+yarn binary-deploy --platform darwin --version 0.20.0
+yarn binary-upload --platform darwin --version 0.20.0 --zip cypress.zip
 ```
 
 If something goes wrong, see the debug messages using the `DEBUG=cypress:binary ...` environment
@@ -76,7 +72,7 @@ Because we had many problems reliably zipping the built binary, for now we need
 If you are using a Mac you can build the linux binary if you have docker installed.
 
 ```shell
-npm run binary-build-linux
+yarn binary-build-linux
 ```
 
 ## Publishing
@@ -121,11 +117,12 @@ In the following instructions, "X.Y.Z" is used to denote the version of Cypress
 2. Use the `move-binaries` script to move the binaries for `<commit sha>` from `beta` to the `desktop` folder
     for `<new target version>`
     ```shell
-    npm run move-binaries -- --sha <commit sha> --version <new target version>
+    yarn move-binaries --sha <commit sha> --version <new target version>
     ```
-3. Publish the new NPM package under the `dev` tag. The unique link to the package file `cypress.tgz` is the one already tested above. You can publish to the NPM registry straight from the URL:
+3. Publish the new NPM package under the dev tag. The unique link to the package file `cypress.tgz`
+    is the one already tested above. You can publish to the NPM registry straight from the URL:
     ```shell
-    npm publish https://cdn.../npm/X.Y.Z/<long sha>/cypress.tgz --tag dev
+    yarn publish https://cdn.../npm/X.Y.Z/<long sha>/cypress.tgz --tag dev
     ```
 4. Double-check that the new version has been published under the `dev` tag using `npm info cypress` or [available-versions](https://github.com/bahmutov/available-versions). Example output:
     ```shell
@@ -140,11 +137,11 @@ In the following instructions, "X.Y.Z" is used to denote the version of Cypress
 7. Update and publish the changelog and any release-specific documentation changes in [cypress-documentation](https://github.com/cypress-io/cypress-documentation).
 8. Make the new NPM version the "latest" version by updating the dist-tag `latest` to point to the new version:
     ```shell
-    npm dist-tag add [email protected]
+    yarn dist-tag add [email protected]
     ```
-9. Run `binary-release` to update the download the server's manifest, set the next CI version, and create an empty version commit:
+8. Run `binary-release` to update the download server's manifest, set the next CI version, and create an empty version commit:
     ```shell
-    npm run binary-release -- --version X.Y.Z --commit
+    yarn run binary-release --version X.Y.Z --commit
     ```
 10. If needed, push out any updated changes to the links manifest to [`on.cypress.io`](https://github.com/cypress-io/cypress-services/tree/develop/packages/on).
 11. If needed, deploy the updated [`cypress-example-kitchensink`][cypress-example-kitchensink] to `example.cypress.io` by following [these instructions under "Deployment"](./packages/example/README.md).

appveyor.yml

@@ -2,6 +2,7 @@ branches:
   only:
     - master
     - develop
+    - issue-5477-replace-npm-with-yarn
     - /win*/
 
 # https://www.appveyor.com/docs/lang/nodejs-iojs/
@@ -40,63 +41,52 @@ platform:
 # with installing over cached folder
 # https://github.com/npm/npm/issues/17747
 # cache:
-#   - node_modules
+#   - node_modules -> yarn.lock
+#   - '%LOCALAPPDATA%/Yarn -> yarn.lock'
 #   # todo: cache node_modules in each package
 
 # Install scripts. (runs after repo cloning)
 install:
   - ps: Install-Product node $env:nodejs_version $env:platform
   # upgrade npm
-  - npm install -g npm@6
-  - npm install -g @bahmutov/print-env@1
+  - yarn global add @bahmutov/print-env@1
   # Output useful info for debugging.
   - node --version
   - node --print process.arch
-  - npm --version
-  - npm run check-next-dev-version
+  - yarn --version
+  - yarn check-next-dev-version
   # prints all public variables relevant to the build
   - print-env Platform
-  - npm run check-node-version
+  - yarn check-node-version
   - print-env APPVEYOR
   # prints if we have sensitive variables that start with a prefix GH
   # which are used to trigger other projects
   - has-env GH
   # clean cache to prevent install permission issues
-  - npm cache clean --force
-  # install root modules only, and retry automatically if install fails
-  - npm run preinstall
-  - npm install --ignore-scripts || npm install --ignore-scripts || npm install --ignore-scripts
+  - yarn cache clean
+  - yarn || yarn || yarn
   - .\node_modules\.bin\print-arch
-  # because we skipped scripts, we need to do
-  # everything from "postinstall" script as commands
-  - npm run link
-  # install every package one by one
-  # try to do several attempts, because on AppVeyor random install errors happen
-  - npm run all install -- --serial || npm run all install -- --serial || npm run all install -- --serial
-  # - npm prune
-  # - npm run all prune -- --serial
-  - npm run all build -- --serial
 
 # Post-install test scripts.
 test_script:
   # Output useful info for debugging.
   # beware of echo-ing environment variables that may have batch syntax (e.g. commit messages)
   - node --version
-  - npm --version
+  - yarn --version
   - 7z
   - cd packages/launcher && node index.js && cd ../..
   # make sure mocha runs
-  - npm run test-mocha
+  - yarn test-mocha
   # make sure our snapshots are compared correctly
   # - npm run test-mocha-snapshot
   # the other larger tests
   - echo Building Windows NPM package %NEXT_DEV_VERSION%
   - npm --no-git-tag-version version %NEXT_DEV_VERSION%
   - cd cli
-  - npm install
-  - npm run build
+  - yarn
+  - yarn build
   - cd build
-  - npm pack
+  - yarn pack
   - cd ../..
 
   - node ./scripts/win-appveyor-build.js