chore: use prettier

.eslintrc.js

@@ -0,0 +1,15 @@
+/* @flow */
+
+module.exports = {
+  extends: require.resolve(
+    "@krakenjs/grumbler-scripts/config/.eslintrc-browser"
+  ),
+
+  rules: {
+    "default-param-last": "off",
+    "func-names": "off",
+    "no-plusplus": "off",
+    "no-commonjs": "off",
+    "flowtype/require-return-type": "off",
+  },
+};

.husky/.gitignore

@@ -0,0 +1 @@
+_

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx lint-staged

.prettierignore

@@ -0,0 +1,4 @@
+build
+dist
+coverage
+flow-typed

.prettierrc.json

@@ -0,0 +1 @@
+{}

.travis.yml

@@ -1,4 +1,4 @@
 language: node_js
 node_js:
-   - "lts/*"
+  - "lts/*"
 script: npm test

CONTRIBUTING.md

@@ -6,7 +6,9 @@ Feel free to raise a pull request to us. Our team would review your proposed mod
 your changes into our code. Ideas and other comments are also welcome.
 
 ## Getting Started
+
 1. Create your own [fork](https://help.github.com/articles/fork-a-repo) of this [repository](../../fork).
+
 ```bash
 # Clone it
 $ git clone [email protected]:me/sync-browser-mocks.git
@@ -30,12 +32,14 @@ $ npm run-script cover
 ```
 
 ## Making Changes
+
 1. Make sure that your changes adhere to the current coding conventions used throughout the project, indentation, accurate comments, etc.
 2. Lint your code regularly and ensure it passes prior to submitting a PR:
-`$ npm run lint`.
+   `$ npm run lint`.
 3. Ensure existing tests pass (`$ npm test`) and include test cases which fail without your change and succeed with it.
 
 ## Submitting Changes
+
 1. Ensure that no errors are generated by ESLint.
 2. Commit your changes in logical chunks, i.e. keep your changes small per single commit.
 3. Locally merge (or rebase) the upstream branch into your topic branch: `$ git pull upstream && git merge`.