chore: update prettier to v2.6.2

Author: sf-v

.github/CODE_OF_CONDUCT.md

@@ -35,23 +35,23 @@ socioeconomic status, or other similar personal characteristics.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy toward other community members
+-   Using welcoming and inclusive language
+-   Being respectful of differing viewpoints and experiences
+-   Gracefully accepting constructive criticism
+-   Focusing on what is best for the community
+-   Showing empathy toward other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Personal attacks, insulting/derogatory comments, or trolling
-* Public or private harassment
-* Publishing, or threatening to publish, others' private information—such as
-a physical or electronic address—without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-professional setting
-* Advocating for or encouraging any of the above behaviors
+-   The use of sexualized language or imagery and unwelcome sexual attention or
+    advances
+-   Personal attacks, insulting/derogatory comments, or trolling
+-   Public or private harassment
+-   Publishing, or threatening to publish, others' private information—such as
+    a physical or electronic address—without explicit permission
+-   Other conduct which could reasonably be considered inappropriate in a
+    professional setting
+-   Advocating for or encouraging any of the above behaviors
 
 ## Our Responsibilities
 
@@ -98,7 +98,7 @@ It includes adaptions and additions from [Go Community Code of Conduct][golang-c
 
 This Code of Conduct is licensed under the [Creative Commons Attribution 3.0 License][cc-by-3-us].
 
-[contributor-covenant-home]: https://www.contributor-covenant.org (https://www.contributor-covenant.org/)
+[contributor-covenant-home]: https://www.contributor-covenant.org 'https://www.contributor-covenant.org/'
 [golang-coc]: https://golang.org/conduct
 [cncf-coc]: https://github.com/cncf/foundation/blob/master/code-of-conduct.md
 [microsoft-coc]: https://opensource.microsoft.com/codeofconduct/

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,26 @@
-
 ## Details
 
-
 ## Does this PR introduce a breaking change?
 
-* [ ] Yes
-* [ ] No
+-   [ ] Yes
+-   [ ] No
 
 If yes, please describe the impact and migration path for existing applications:
 Please check if your PR fulfills the following requirements:
 
-
 ## Reminders ( please delete this section before submitting )
--------------------------------------------------------------
+
+---
 
 ### The PR fulfills these requirements:
-* Tests for the changes have been added (for bug fixes / features)
-* Docs have been added / updated (for bug fixes / features)
+
+-   Tests for the changes have been added (for bug fixes / features)
+-   Docs have been added / updated (for bug fixes / features)
 
 ### PR Title
+
 Your PR title should following the format below and is automatically validated by our CI.
+
 ```shell
 ex:
 commit-type(optional scope): commit description. ( NOTE: space between column and the message )

.prettierignore

@@ -1,7 +1,8 @@
 .github/
+__benchmarks_results__/
 build/
+CHANGELOG.md
 coverage/
-__benchmarks_results__/
-public/
 examples
-CHANGELOG.md
+fixtures/
+public/

CHANGELOG.md

@@ -21,4 +21,3 @@ cd packages/@best/agent-frontend
 yarn watch
 
 ```
-

LOCAL_DEV.md

@@ -22,8 +22,7 @@ that allows you to monitor your benchmarks over the time with each commit.
 
 ## Getting Started
 
-Ready to jump in? We recommend starting with [The "Best" Manifesto][best
-introduction] first, and then once you have a solid understanding of how
+Ready to jump in? We recommend starting with [The "Best" Manifesto][best introduction] first, and then once you have a solid understanding of how
 Best works, checking out the [Developer Guide][getting started] to read
 about how to get started!
 

README.md

@@ -1,10 +1,8 @@
 module.exports = {
-    presets: [
-        "@babel/preset-typescript"
-    ],
+    presets: ['@babel/preset-typescript'],
     plugins: [
-        "@babel/plugin-proposal-class-properties",
-        "@babel/transform-modules-commonjs",
-        "@babel/plugin-syntax-dynamic-import"
-    ]
-}
+        '@babel/plugin-proposal-class-properties',
+        '@babel/transform-modules-commonjs',
+        '@babel/plugin-syntax-dynamic-import',
+    ],
+};

babel.config.js

@@ -6,7 +6,7 @@
  */
 module.exports = {
     extends: [
-        '@commitlint/config-conventional' // scoped packages are not prefixed
+        '@commitlint/config-conventional', // scoped packages are not prefixed
     ],
     rules: {
         'type-enum': [
@@ -26,8 +26,8 @@ module.exports = {
                 'revert',
                 'style',
                 'test',
-                'wip'
-            ]
-        ]
-    }
+                'wip',
+            ],
+        ],
+    },
 };

commitlint.config.js

@@ -8,11 +8,11 @@ module.exports = {
             'continuous-integration',
             'github-integration',
             'frontend',
-            'configuration'
+            'configuration',
         ],
     },
     blog: {
-        latest: 'welcome_to_best'
+        latest: 'welcome_to_best',
         // pages are discovered and ordered automatically
     },
 };

docs/config.js

@@ -6,4 +6,4 @@ created_at: 'May 20, 2019'
 
 # Behold!
 
-Yay!
+Yay!

docs/content/blog/old_post.md

@@ -6,9 +6,9 @@ title: Configuration
 
 Best is highly configurable through command-line arguments, the Best configuration file, and environment variables.
 
-- [Command Line Arguments](#command-line-arguments)
-- [Best Configuration File](#best-configuration-file)
-- [Environment Variables](#environment-variables)
+-   [Command Line Arguments](#command-line-arguments)
+-   [Best Configuration File](#best-configuration-file)
+-   [Environment Variables](#environment-variables)
 
 ## Command Line Arguments
 
@@ -139,12 +139,15 @@ When `alias` is specified the assets are served from that path, for example `/as
 
 ```js
 {
-    assets: [{
-        path: './public/'
-    }, {
-        alias: '/assets',
-        path: '/path/to/node_modules/my-static-assets/dist/'
-    }]
+    assets: [
+        {
+            path: './public/',
+        },
+        {
+            alias: '/assets',
+            path: '/path/to/node_modules/my-static-assets/dist/',
+        },
+    ];
 }
 ```
 
@@ -169,7 +172,7 @@ When `alias` is specified the assets are served from that path, for example `/as
     plugins: [
         ['@lwc/rollup-plugin', { rootDir: '<rootDir>/src/' }],
         ['rollup-plugin-replace', { 'process.env.NODE_ENV': JSON.stringify('production') }],
-    ]
+    ];
 }
 ```
 
@@ -187,25 +190,25 @@ For the headless runner, [Puppeteer launch options](https://github.com/puppeteer
 {
     runners: [
         {
-            runner: "@best/runner-headless",
-            alias: "default",
+            runner: '@best/runner-headless',
+            alias: 'default',
             config: {
                 launchOptions: {
                     headless: false,
-                    devtools: true
-                }
-            }
+                    devtools: true,
+                },
+            },
         },
         {
-            runner: "@best/runner-remote",
-            alias: "remote-agent",
+            runner: '@best/runner-remote',
+            alias: 'remote-agent',
             config: {
-                host: "http://localhost:5000",
-                options: { path: "/best" },
-                remoteRunner: "@best/runner-headless"
-            }
+                host: 'http://localhost:5000',
+                options: { path: '/best' },
+                remoteRunner: '@best/runner-headless',
+            },
         },
-    ]
+    ];
 }
 ```
 

docs/content/docs/configuration.md

@@ -29,11 +29,11 @@ To see an example, look at Best's own CircleCI [`config.yml`](https://github.com
 
 ```yml
 - run:
-    name: Run BEST Benchmarks
-    command: yarn perf
+      name: Run BEST Benchmarks
+      command: yarn perf
 - run:
-    name: Compare BEST Benchmarks
-    command: yarn perf --compareStats ${BASE_COMMIT} ${TARGET_COMMIT} --gitIntegration
+      name: Compare BEST Benchmarks
+      command: yarn perf --compareStats ${BASE_COMMIT} ${TARGET_COMMIT} --gitIntegration
 ```
 
 The Yarn command `perf` is essentially an alias to the Best CLI. Best is first run to benchmark the code of the new Pull Request. Then `best --compareStats` is run with a base commit from `master` and a target commit from the PR. The `--gitIntegration` flag causes Best to post the results on the pull request on GitHub.

docs/content/docs/continuous-integration.md

@@ -34,16 +34,16 @@ You can create your own server to host the front end. Follow [this template](htt
 
     ```js
     import express from 'express';
-    import { Frontend } from '@best/frontend'
-    import config from './best-frontend.config'
+    import { Frontend } from '@best/frontend';
+    import config from './best-frontend.config';
 
-    const PORT = process.env.PORT || 3000
+    const PORT = process.env.PORT || 3000;
 
-    const app = express()
+    const app = express();
 
-    app.use(Frontend(config))
+    app.use(Frontend(config));
 
-    app.listen(PORT)
+    app.listen(PORT);
     ```
 
 1. This code is the `best-frontend.confg` configuration file.
@@ -52,13 +52,14 @@ You can create your own server to host the front end. Follow [this template](htt
     export default {
         apiDatabase: {
             adapter: 'sql/postgres',
-            uri: 'postgresql://localhost' // Provide the connection URI to your hosted postgres database
+            uri: 'postgresql://localhost', // Provide the connection URI to your hosted postgres database
         },
-        githubConfig: { // (optional) Allows the frontend to fetch commit info directly from GitHub
+        githubConfig: {
+            // (optional) Allows the frontend to fetch commit info directly from GitHub
             owner: 'salesforce',
-            repo: 'best'
-        }
-    }
+            repo: 'best',
+        },
+    };
     ```
 
 1. Start the server and point your browser as its URL.

docs/content/docs/frontend.md

@@ -22,7 +22,7 @@ Now that you have Best installed, you can start writing some benchmarks. We reco
 
 Let's look at some examples of what a benchmark might look like. Your benchmarks should be in a file ending in `.benchmark.js`.
 
-This is a very simple example of what a benchmark might look like. 
+This is a very simple example of what a benchmark might look like.
 
 ```js
 import fib from '../fib';
@@ -31,15 +31,15 @@ describe('js-execution', () => {
     benchmark('fibonacci 15', () => {
         run(() => {
             return fib(15);
-        })
-    })
+        });
+    });
 
     benchmark('fibonacci 38', () => {
         run(() => {
             return fib(38);
-        })
-    })
-})
+        });
+    });
+});
 ```
 
 Now let's look at one that uses [Lightning Web Components](https://lwc.dev) that interacts with the DOM.
@@ -55,12 +55,12 @@ describe('simple-item', () => {
             element = createElement('simple-item', { is: SimpleItem });
             element.flavor = 'red';
             document.body.appendChild(element);
-        })
+        });
         after(() => {
             return element && element.parentElement.removeChild(element);
-        })
-    })
-})
+        });
+    });
+});
 ```
 
 Here we have also added an `after` block to clean up the DOM after our test. This resets the state properly between each benchmark.
@@ -75,8 +75,8 @@ There is one last step before you can run the benchmarks: create a `best.config.
 
 ```js
 module.exports = {
-    projectName: 'my-benchmarks'
-}
+    projectName: 'my-benchmarks',
+};
 ```
 
 To further customize your Best setup, read about [configuration](/guide/configuration#best-configuration).

docs/content/docs/getting-started.md

@@ -12,9 +12,9 @@ Best relies on a GitHub app to interact with your repositories. Follow [GitHub's
 
 The GitHub App requires these permissions:
 
-- **Checks**: Read/Write
-- **Issues**: Read/Write
-- **Pull Requests**: Read/Write
+-   **Checks**: Read/Write
+-   **Issues**: Read/Write
+-   **Pull Requests**: Read/Write
 
 Set these environment variables so Best can authenticate and interact with your GitHub App. We recommended setting these environment variables in your CI.
 
@@ -46,6 +46,6 @@ By default, Best comments on a pull request when the average performance across
 
 ```js
 {
-    commentThreshold: 5
+    commentThreshold: 5;
 }
 ```