chore: remove the cli.js development utility (#151)

* chore: remove the cli.js development utility

Also, add a `CONTRIBUTING.md` file to document. This is primarily to
document how devs can run the code locally (`node bin/dist.js ...`).

* chore: 'yarn remove rimraf'

removed because vendor/fetch-docs.js was our only use of it

* docs: fix the docs-parser invocation

* fix: remove oops

* fixup! fix: remove oops

Author: ckerr

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+# Contributing to electron-typescript-definitions
+
+## Code of Conduct
+
+This project adheres to Electron's [code of conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
+
+## Developing Locally
+
+Building locally to try out changes can be done this way:
+
+```sh
+$ git clone [email protected]:electron/typescript-definitions.git
+$ cd typescript-definitions
+$ yarn install
+$ # make your changes...
+$ yarn build
+```
+
+To run it, first you'll need a `electron-api.json` file. There are a few common ways to get this:
+
+From a [electron/docs-parser](https://github.com/electron/docs-parser) repo (since working on this often goes hand-in-hand wth typescript-definitions):
+
+```sh
+$ cd docs-parser
+$ yarn install
+$ yarn build && node dist/bin.js --dir /path/to/electron-gn/src/electron
+```
+
+From a [electron/electron](https://github.com/electron/electron/) repo:
+
+```sh
+$ cd /path/to/electron-gn/src/electron
+$ npm install
+$ npm run create-api-json
+```
+
+Either way, once you have `electron-api.json`, run it through the typescript generator:
+
+```sh
+$ cd typescript-definitions
+$ yarn build && node dist/bin.js --api /path/to/electron-api.json
+```

cli.js

@@ -46,7 +46,6 @@
     "mkdirp": "^0.5.1",
     "ora": "^3.4.0",
     "pretty-ms": "^5.0.0",
-    "rimraf": "^2.5.4",
     "typescript": "^3.4.5"
   },
   "repository": {