feat(base) added base layout for app (#1)

* feat(base) POC

* feat(eslint) added eslint

Author: ImmanuelSegol

.env

@@ -0,0 +1 @@
+SKIP_PREFLIGHT_CHECK=true

.eslintrc

@@ -0,0 +1,45 @@
+{
+    "parser": "babel-eslint",
+    "plugins": [
+      "prettier",
+      "react"
+    ],
+    "parserOptions": {
+      "ecmaVersion": 2017,
+      "sourceType": "module",
+      "ecmaFeatures": {
+        "jsx": true,
+        "spread": true,
+        "experimentalObjectRestSpread": true
+      }
+    },
+    "globals": {
+      "__DEV__": true,
+      "fetch": true,
+      "Promise": true,
+      "window": true,
+      "document": true,
+      "navigator": true
+    },
+    "env": {
+      "es6": true,
+      "node": true
+    },
+    "extends": [
+      "eslint:recommended",
+      "plugin:react/recommended",
+      "prettier"
+    ],
+    "rules": {
+      "max-len": [1, 120, 2, {"ignoreComments": true}],
+      "prop-types": [0],
+      "prettier/prettier": ["error", {
+        "singleQuote": true,
+        "trailingComma": "es5",
+        "bracketSpacing": true,
+        "jsxBracketSameLine": false,
+        "parser": "babylon"
+      }],
+      "no-console": "off"
+    }
+  }

.git-commit-template.txt

@@ -0,0 +1,31 @@
+# HEADER
+# |<----  Using a Maximum Of 50 Characters  ---->|
+<type>(<scope>): <subject>
+# Type can be 
+#    feat     (A new feature)
+#    fix      (A bug fix)
+#    docs     (Documentation only changes)
+#    style    (Changes that do not affect the meaning of the code e.g. white-space, formatting, missing semi-colons, etc)
+#    refactor (A code change that neither fixes a bug nor adds a feature)
+#    perf     (A code change that improves performance)
+#    test     (Adding missing or correcting existing tests)
+#    chore    (Changes to the build process or auxiliary tools and libraries such as documentation generation)
+# An optional scope specifies the place of the commit change, e.g. orderbook, p2p, proto, swaps, etc...
+# You can use * when the change affects more than a single scope.
+# The subject contains succinct description of the change:
+#    Use the imperative, present tense: "change" not "changed" nor "changes"
+#    Don't capitalize first letter
+#    No dot (.) at the end
+
+# BODY
+# Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes".
+# The body should include the motivation for the change and contrast this with previous behavior.
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->
+
+
+# FOOTER
+# The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit closes.
+# Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->
+
+# --- COMMIT END ---

.gitignore

@@ -0,0 +1,23 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# production
+/build
+
+# misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

.travis.yml

@@ -0,0 +1,9 @@
+language: node_js
+node_js:
+  - "lts/*"
+cache:
+  directories:
+  - node_modules
+script:
+  - npm lint
+  - npm run build