Set up and run Prettier over entire codebase. (#1076)

.eslintignore

@@ -1 +1,2 @@
 /lib-es5
+/test

.github/workflows/ci.yml

@@ -8,7 +8,6 @@ on:
 
 jobs:
   test:
-
     strategy:
       fail-fast: false # prevent test to stop if one fails
       matrix:

.prettierignore

@@ -0,0 +1 @@
+lib-es5/

README.md

@@ -11,15 +11,15 @@ This command line interface enables you to package your Node.js project into an
 
 ## Use Cases
 
-* Make a commercial version of your application without sources
-* Make a demo/evaluation/trial version of your app without sources
-* Instantly make executables for other platforms (cross-compilation)
-* Make some kind of self-extracting archive or installer
-* No need to install Node.js and npm to run the packaged application
-* No need to download hundreds of files via `npm install` to deploy
-your application. Deploy it as a single file
-* Put your assets inside the executable to make it even more portable
-* Test your app against new Node.js version without installing it
+- Make a commercial version of your application without sources
+- Make a demo/evaluation/trial version of your app without sources
+- Instantly make executables for other platforms (cross-compilation)
+- Make some kind of self-extracting archive or installer
+- No need to install Node.js and npm to run the packaged application
+- No need to download hundreds of files via `npm install` to deploy
+  your application. Deploy it as a single file
+- Put your assets inside the executable to make it even more portable
+- Test your app against new Node.js version without installing it
 
 ## Usage
 
@@ -31,12 +31,12 @@ After installing it, run `pkg --help` without arguments to see list of options.
 
 The entrypoint of your project is a mandatory CLI argument. It may be:
 
-* Path to entry file. Suppose it is `/path/app.js`, then
-packaged app will work the same way as `node /path/app.js`
-* Path to `package.json`. `Pkg` will follow `bin` property of
-the specified `package.json` and use it as entry file.
-* Path to directory. `Pkg` will look for `package.json` in
-the specified directory. See above.
+- Path to entry file. Suppose it is `/path/app.js`, then
+  packaged app will work the same way as `node /path/app.js`
+- Path to `package.json`. `Pkg` will follow `bin` property of
+  the specified `package.json` and use it as entry file.
+- Path to directory. `Pkg` will look for `package.json` in
+  the specified directory. See above.
 
 ### Targets
 
@@ -45,9 +45,9 @@ time. You can specify a comma-separated list of targets via `--targets`
 option. A canonical target consists of 3 elements, separated by
 dashes, for example `node6-macos-x64` or `node4-linux-armv6`:
 
-* **nodeRange** node${n} or latest
-* **platform** freebsd, linux, alpine, macos, win
-* **arch** x64, x86, armv6, armv7
+- **nodeRange** node${n} or latest
+- **platform** freebsd, linux, alpine, macos, win
+- **arch** x64, x86, armv6, armv7
 
 You may omit any element (and specify just `node6` for example).
 The omitted elements will be taken from current platform or
@@ -65,23 +65,29 @@ don't need to specify anything manually. However your code
 may have `require(variable)` calls (so called non-literal
 argument to `require`) or use non-javascript files (for
 example views, css, images etc).
+
 ```js
-  require('./build/' + cmd + '.js')
-  path.join(__dirname, 'views/' + viewName)
+require('./build/' + cmd + '.js');
+path.join(__dirname, 'views/' + viewName);
 ```
+
 Such cases are not handled by `pkg`. So you must specify the
 files - scripts and assets - manually in `pkg` property of
 your `package.json` file.
+
 ```json
   "pkg": {
     "scripts": "build/**/*.js",
     "assets": "views/**/*"
   }
 ```
+
 You may also specify arrays of globs:
+
 ```
     "assets": [ "assets/**/*", "images/**/*" ]
 ```
+
 Just be sure to call `pkg package.json` or `pkg .` to make use
 of `scripts` and `assets` entries.
 
@@ -113,6 +119,7 @@ Node.js application can be called with runtime options
 `node --v8-options`. You can "bake" these runtime options into
 packaged application. The app will always run with the options
 turned on. Just remove `--` from option name.
+
 ```sh
 pkg app.js --options expose-gc
 pkg app.js --options max_old_space_size=4096
@@ -143,11 +150,11 @@ requirements to compile original Node.js:
 
 ### Environment
 
-| Var            | Description                                                                             |
-| -------------- | --------------------------------------------------------------------------------------- |
-| PKG_CACHE_PATH | Used to specify a custom path for node binaries cache folder. Default is `~/.pkg-cache` |
+| Var            | Description                                                                               |
+| -------------- | ----------------------------------------------------------------------------------------- |
+| PKG_CACHE_PATH | Used to specify a custom path for node binaries cache folder. Default is `~/.pkg-cache`   |
 | PKG_IGNORE_TAG | Allows to ignore additional folder created on `PKG_CACHE_PATH` matching pkg-fetch version |
-| MAKE_JOB_COUNT | Allow configuring number of processes used for compiling |
+| MAKE_JOB_COUNT | Allow configuring number of processes used for compiling                                  |
 
 Examples
 
@@ -178,17 +185,17 @@ then `__filename` value will be likely `/snapshot/path/app.js`
 at run time. `__dirname` will be `/snapshot/path` as well. Here is
 the comparison table of path-related values:
 
-value                          | with `node`         | packaged                   | comments
--------------------------------|---------------------|----------------------------|-----------
-__filename                     | /project/app.js     | /snapshot/project/app.js   |
-__dirname                      | /project            | /snapshot/project          |
-process.cwd()                  | /project            | /deploy                    | suppose the app is called ...
-process.execPath               | /usr/bin/nodejs     | /deploy/app-x64            | `app-x64` and run in `/deploy`
-process.argv[0]                | /usr/bin/nodejs     | /deploy/app-x64            |
-process.argv[1]                | /project/app.js     | /snapshot/project/app.js   |
-process.pkg.entrypoint         | undefined           | /snapshot/project/app.js   |
-process.pkg.defaultEntrypoint  | undefined           | /snapshot/project/app.js   |
-require.main.filename          | /project/app.js     | /snapshot/project/app.js   |
+| value                         | with `node`     | packaged                 | comments                       |
+| ----------------------------- | --------------- | ------------------------ | ------------------------------ |
+| \_\_filename                  | /project/app.js | /snapshot/project/app.js |
+| \_\_dirname                   | /project        | /snapshot/project        |
+| process.cwd()                 | /project        | /deploy                  | suppose the app is called ...  |
+| process.execPath              | /usr/bin/nodejs | /deploy/app-x64          | `app-x64` and run in `/deploy` |
+| process.argv[0]               | /usr/bin/nodejs | /deploy/app-x64          |
+| process.argv[1]               | /project/app.js | /snapshot/project/app.js |
+| process.pkg.entrypoint        | undefined       | /snapshot/project/app.js |
+| process.pkg.defaultEntrypoint | undefined       | /snapshot/project/app.js |
+| require.main.filename         | /project/app.js | /snapshot/project/app.js |
 
 Hence, in order to make use of a file collected at packaging
 time (`require` a javascript file or serve an asset) you should
@@ -243,7 +250,7 @@ with `.node` files.
 a promise. For example:
 
 ```js
-await exec([ 'app.js', '--target', 'host', '--output', 'app.exe' ])
+await exec(['app.js', '--target', 'host', '--output', 'app.exe']);
 // do something with app.exe, run, test, upload, deploy, etc
 ```
 
@@ -272,4 +279,4 @@ You could check on **Unix systems** (Linux/macOS) in `bash`:
 
 ```bash
 $ printenv | grep NODE
-```
+```

appveyor.yml

@@ -1,5 +1,5 @@
 environment:
-  nodejs_version: "12"
+  nodejs_version: '12'
 
 install:
   - ps: Install-Product node $env:nodejs_version x64

dictionary/angular-bridge.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/any-promise.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/async.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/aws-sdk.js

@@ -2,9 +2,6 @@
 
 module.exports = {
   pkg: {
-    scripts: [
-      'apis/*.json',
-      'lib/services/*.js'
-    ]
-  }
+    scripts: ['apis/*.json', 'lib/services/*.js'],
+  },
 };

dictionary/babel-core.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/batch.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/bcrypt.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/bignum.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/bindings.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/blessed.js

@@ -3,8 +3,6 @@
 // https://github.com/chjj/blessed/issues/298
 module.exports = {
   pkg: {
-    scripts: [
-      'lib/widgets/*.js'
-    ]
-  }
+    scripts: ['lib/widgets/*.js'],
+  },
 };

dictionary/body-parser.js

@@ -3,7 +3,7 @@
 module.exports = {
   pkg: {
     scripts: [
-      'lib/types/*.js' // for 1.4-1.13
-    ]
-  }
+      'lib/types/*.js', // for 1.4-1.13
+    ],
+  },
 };

dictionary/browserify.js

@@ -2,8 +2,6 @@
 
 module.exports = {
   pkg: {
-    assets: [
-      'bin/*.txt'
-    ]
-  }
+    assets: ['bin/*.txt'],
+  },
 };

dictionary/bson.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/buffermaker.js

@@ -2,8 +2,6 @@
 
 module.exports = {
   pkg: {
-    scripts: [
-      'lib/*.js'
-    ]
-  }
+    scripts: ['lib/*.js'],
+  },
 };

dictionary/bunyan.js

@@ -3,10 +3,7 @@
 module.exports = {
   pkg: {
     patches: {
-      'lib/bunyan.js': [
-        'mv = require(\'mv\' + \'\');',
-        'mv = require(\'mv\');'
-      ]
-    }
-  }
+      'lib/bunyan.js': ["mv = require('mv' + '');", "mv = require('mv');"],
+    },
+  },
 };

dictionary/busboy.js

@@ -2,8 +2,6 @@
 
 module.exports = {
   pkg: {
-    scripts: [
-      'lib/types/*.js'
-    ]
-  }
+    scripts: ['lib/types/*.js'],
+  },
 };

dictionary/bytes.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/callsites.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/chokidar.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/coffee-script.js

@@ -2,8 +2,6 @@
 
 module.exports = {
   pkg: {
-    scripts: [
-      'lib/coffee-script/*.js'
-    ]
-  }
+    scripts: ['lib/coffee-script/*.js'],
+  },
 };

dictionary/colors.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/compression.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/compressjs.js

@@ -2,8 +2,6 @@
 
 module.exports = {
   pkg: {
-    scripts: [
-      'lib/*.js'
-    ]
-  }
+    scripts: ['lib/*.js'],
+  },
 };

dictionary/connect-mongo.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/connect-mongodb.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};

dictionary/connect-redis.js

@@ -1,4 +1,3 @@
 'use strict';
 
-module.exports = {
-};
+module.exports = {};