Switch from npm to Yarn

The proximate cause is npm/npm#17722, although perhaps we'll find more benefits.

Author: Zirro

.gitignore

@@ -4,6 +4,7 @@
 gmon.out
 v8.log
 node_modules
+package-lock.json
 test/worker-bundle.js
 test/web-platform-tests/tuwpt-manifest.json
 npm-debug.log*

.travis.yml

@@ -8,8 +8,8 @@ git:
   submodules: false
 
 script:
-  - npm run lint
-  - npm test
+  - yarn lint
+  - yarn test
 
 branches:
   only:
@@ -28,7 +28,7 @@ matrix:
   include:
     - node_js: 6
       env: TEST_SUITE=node-canvas-prebuilt
-      script: "export CXX=g++-4.8 && npm i canvas-prebuilt && npm test"
+      script: "export CXX=g++-4.8 && yarn add canvas-prebuilt && yarn test"
       addons:
         hosts:
           - web-platform.test
@@ -39,7 +39,7 @@ matrix:
           - xn--lve-6lad.web-platform.test
     - node_js: 6
       env: TEST_SUITE=node-canvas
-      script: "export CXX=g++-4.8 && npm i canvas && npm test"
+      script: "export CXX=g++-4.8 && yarn add canvas && yarn test"
       addons:
         hosts:
           - web-platform.test
@@ -60,7 +60,7 @@ matrix:
             - build-essential
     - node_js: stable
       env: TEST_SUITE=node-canvas
-      script: "export CXX=g++-4.8 && npm i canvas && npm test"
+      script: "export CXX=g++-4.8 && yarn add canvas && yarn test"
       addons:
         hosts:
           - web-platform.test
@@ -79,7 +79,7 @@ matrix:
             - libpango1.0-dev
             - libgif-dev
             - build-essential
-    - script: '[ "${TRAVIS_PULL_REQUEST}" != "false" ] || (npm run pretest && npm run test-browser)'
+    - script: '[ "${TRAVIS_PULL_REQUEST}" != "false" ] || (yarn run pretest && yarn run test-browser)'
       env: TEST_SUITE=browser
       addons:
         sauce_connect:

Contributing.md

@@ -2,6 +2,12 @@
 
 jsdom is, as said in our tagline, “A JavaScript implementation of the DOM and HTML standards.” Anything that helps us be better at that is welcome.
 
+## Yarn
+
+We use the [Yarn](https://yarnpkg.com/) package manager to manage dependencies and run the scripts defined in `package.json`. It is similar to npm, but contains fewer bugs for our purposes. If you make changes which add or remove dependencies, make sure you commit the `yarn.lock` file which it generates.
+
+You can probably get away with using npm for most contributions, as long as you are not adding or removing dependencies. You'll have to mentally translate the Yarn commands we give into npm ones, however.
+
 ## Architecture
 
 jsdom is a blend of old and new code. Some of its older and less-touched corners may look different from newer work. Here we'll describe the modern setup, but you might encounter parts of the codebase that don't fit this model, or that seem unnecessarily baroque (like the directory structure in `lib/`).
@@ -13,7 +19,7 @@ As such, most web platform classes present in jsdom are implemented in two parts
 - An IDL file, such as [`Attr.idl`](https://github.com/tmpvar/jsdom/blob/master/lib/jsdom/living/attributes/Attr.idl), drawn more or less straight from the spec
 - An implementation file, such as [`Attr-impl.js`](https://github.com/tmpvar/jsdom/blob/master/lib/jsdom/living/attributes/Attr-impl.js), containing the relevant implementation logic
 
-Our build step (`npm run prepublish`) then generates a public API file (e.g. `Attr.js`) which takes care of all the Web IDL-derived boilerplate, delegating to the implementation file for the important stuff. We then wire it together with a line in `lib/jsdom/living/index.js` that exposes the generated class on all jsdom windows.
+Our build step (`yarn prepare`) then generates a public API file (e.g. `Attr.js`) which takes care of all the Web IDL-derived boilerplate, delegating to the implementation file for the important stuff. We then wire it together with a line in `lib/jsdom/living/index.js` that exposes the generated class on all jsdom windows.
 
 ## Contribution overview
 
@@ -33,61 +39,61 @@ Other specs might pop up from time to time, especially in regard to CSS stuff. I
 
 ### Running the tests
 
-First you'll want to `npm install`. Then, configure your system to run the web platform tests as described in [their README](https://github.com/w3c/web-platform-tests/blob/master/README.md). If you can't get that set up correctly, the test runner will make a best-faith effort to run the tests hosted on http://w3c-test.org/, but this is pretty slow and fragile.
+First you'll want to run `yarn` to install all dependencies. Then, configure your system to run the web platform tests as described in [their README](https://github.com/w3c/web-platform-tests/blob/master/README.md). If you can't get that set up correctly, the test runner will make a best-faith effort to run the tests hosted on http://w3c-test.org/, but this is pretty slow and fragile.
 
-**To run all the tests:** `npm test`
+**To run all the tests:** `yarn test`
 
 ### Web platform feature tests
 
 All tests for web platform features (as opposed to features of jsdom itself, such as the `JSDOM()` constructor) should be in [web-platform-tests](https://github.com/w3c/web-platform-tests) format. We have some infrastructure for running these directly against jsdom documents. So ideally, when contributing a bugfix or new feature, you can browse the web-platform-tests repository and find the test covering your work, and then just enable it in [the `to-run.yaml` file](https://github.com/tmpvar/jsdom/blob/master/test/web-platform-tests/to-run.yaml). These tests are HTML files which use a special library called [testharness.js](http://testthewebforward.org/docs/testharness-library.html) to report their results.
 
 However, the web-platform-tests project is not fully comprehensive. If you need to write your own test for a web platform feature, place it in our [to-upstream](https://github.com/tmpvar/jsdom/tree/master/test/web-platform-tests/to-upstream) directory. (It's so named because, over time, we hope to upstream these tests back to the web-platform-tests repository, so all browsers can benefit from them.) Note that you may need to create new directory structure, paralleling that of the main [web-platform-tests](https://github.com/w3c/web-platform-tests) repository.
 
-**To run all web-platform-tests:** `npm run test-wpt`
+**To run all web-platform-tests:** `yarn test-wpt`
 
-**To run the to-upstream web-platform-tests:** `npm run test-tuwpt`
+**To run the to-upstream web-platform-tests:** `yarn test-tuwpt`
 
-**To run specific web-platform-tests already enabled via `to-run.yaml`**: `npm run test-wpt -- --fgrep dom/events`
+**To run specific web-platform-tests already enabled via `to-run.yaml`**: `yarn test-wpt -- --fgrep dom/events`
 
-**To run specific to-upstream web-platform-tests**: `npm run test-tuwpt -- --fgrep domparsing`
+**To run specific to-upstream web-platform-tests**: `yarn test-tuwpt -- --fgrep domparsing`
 
-Also, to update web platform tests to their latest revision from the source repository: `npm run update-wpt`. (This can take a long time.)
+Also, to update web platform tests to their latest revision from the source repository: `yarn update-wpt`. (This can take a long time, like 10 minutes.)
 
 ### jsdom API tests
 
 If you are testing something that can only be accomplished through the jsdom API, and not inside a normal web browser, you'll want to write a different kind of test. Such tests are written using [Mocha](https://mochajs.org/) and [Chai](http://chaijs.com/).
 
 To write such a test that, simply add a file in `test/api/`, following the surrounding conventions. Then, add it to the manifest at `test/index.js`.
 
-**To run all API tests:** `npm run test-api`
+**To run all API tests:** `yarn test-api`
 
-**To run a specific API test:** `npm run test-mocha -- test/api/from-file.js`
+**To run a specific API test:** `yarn test-mocha -- test/api/from-file.js`
 
 ### Older tests
 
-Although ideally you should not need to worry about this, there are some tests that are for legacy reasons not in the right format; they use Mocha, but really should be web platform tests. We're keeping them around for coverage until we can convert them. If you run `npm test`, you will get the full test suite, including such old tests.
+Although ideally you should not need to worry about this, there are some tests that are for legacy reasons not in the right format; they use Mocha, but really should be web platform tests. We're keeping them around for coverage until we can convert them. If you run `yarn test`, you will get the full test suite, including such old tests.
 
 ### Testing against the browser
 
 jsdom has experimental support to run in directly in a browser, in both the main document and in a web worker! So we try run as many tests as possible in browsers too. Currently we only test in Chrome, since it has the same JavaScript features as the Node.js environment we usually develop in. So you'll need Chrome installed on your machine.
 
 The mocha test cases are executed in Chrome using [karma](https://karma-runner.github.io/). Currently, web platform tests are not executed in the browser yet.
 
-**To run all browser tests:** `npm run test-browser`
+**To run all browser tests:** `yarn test-browser`
 
-**To run the karma tests in an iframe:** `npm run test-browser-iframe`
+**To run the karma tests in an iframe:** `yarn test-browser-iframe`
 
-**To run the karma tests in a web worker:** `npm run test-browser-worker`
+**To run the karma tests in a web worker:** `yarn test-browser-worker`
 
 ## Benchmarks
 
 This project cares about performance. There are a number of benchmarks that you can run. If you suspect your contribution has an impact on the performance of existing functionality, make sure you run the benchmarks before and after your change so that you can compare.
 
 You can also run the benchmarks using the native DOM implementation of Chrome. A comparison with jsdom will automatically be made for you. If your new feature is much slower than the alternative DOM implementation, there might be an unexpected bottleneck somewhere in your change.
 
-**To run benchmarks in Node.js:** `npm run benchmark`
+**To run benchmarks in Node.js:** `yarn benchmark`
 
-**To run benchmarks in the browser:** `npm run benchmark-browser`, then open `benchmark/browser-runner.html` in Chrome (or Chromium) and use the developer console to execute the `run()` function.
+**To run benchmarks in the browser:** `yarn benchmark-browser`, then open `benchmark/browser-runner.html` in Chrome (or Chromium) and use the developer console to execute the `run()` function.
 
 ## Issues