initial commit

.babelrc

@@ -0,0 +1,18 @@
+{
+  "presets": [
+    [
+      "env",
+      {
+        "browsers": ["last 2 versions", "> 10%", "ie 9"],
+        "modules": false
+      }
+    ],
+    "react",
+    "es2015",
+    "stage-0"
+  ],
+  "plugins": [
+    "react-hot-loader/babel",
+    "syntax-dynamic-import"
+  ]
+}

.circleci/config.yml

@@ -0,0 +1,42 @@
+---
+version: 2
+
+jobs:
+  deploy:
+    docker:
+      - image: circleci/node:10
+    steps:
+      - checkout
+      - restore_cache:
+          keys:
+            - node_modules-{{ checksum "package-lock.json" }}
+
+      - run: |
+          # Get values specific to the environment we are deploying to
+          eval "CURRENT_ENVIRONMENT=\${ENVIRONMENT_$(echo "${CIRCLE_TAG//-/_}" | cut -d\/ -f 2)}"
+          set -a; eval $(echo $CURRENT_ENVIRONMENT | base64 -d); set +a
+
+          npm install
+          NODE_ENV=production npm run build
+
+          sudo apt-get install awscli
+          aws s3 sync dist/ s3://$FRONTEND_BUCKET/dist
+
+          aws configure set preview.cloudfront true
+          aws cloudfront create-invalidation --distribution-id "$CLOUDFRONT_DISTRIBUTION" --paths "/*"
+
+      - save_cache:
+          key: node_modules-{{ checksum "package-lock.json" }}
+          paths:
+            - node_modules
+
+workflows:
+  version: 2
+  deploy:
+    jobs:
+      - deploy:
+          filters:
+            branches:
+              ignore: /.*/
+            tags:
+              only: /env\/.*\/.*/

.dockerignore

@@ -0,0 +1,3 @@
+.git
+dist
+node_modules

.eslintrc

@@ -0,0 +1,43 @@
+{
+  "globals": {
+    "window": true,
+    "document": true,
+    "DEV": true,
+    "DEPLOYED_ADDRESS": true,
+    "artifacts": true,
+  },
+  "parser": "babel-eslint",
+  "extends": [
+    "eslint:recommended",
+    "plugin:react/recommended",
+    "airbnb"
+  ],
+  "rules": {
+    "arrow-parens": 0,
+    "comma-dangle": ["error", "always-multiline"],
+    "global-require": 0,
+    "func-names": 0,
+    "function-paren-newline": 0,
+    "semi": 0,
+    "prefer-arrow-callback": 0,
+    "eqeqeq": 0,
+    "wrap-iife": 0,
+    "no-unused-expressions": 0,
+    "no-console": 0,
+    "no-bitwise": 0,
+    "no-plusplus": 0,
+    "no-multi-assign": 0,
+    "jsx-a11y/anchor-is-valid": 0,
+    "jsx-a11y/no-static-element-interactions": 0,
+    "jsx-a11y/click-events-have-key-events": 0,
+    "jsx-a11y/alt-text": 0,
+    "import/no-unresolved": false,
+    "import/prefer-default-export": false,
+    "import/extensions": false,
+    "import/no-extraneous-dependencies": 0,
+    "react/jsx-filename-extension": false,
+    "no-return-assign": 0,
+    "default-case": 0,
+    "consistent-return": 0,
+  }
+}

.github/CODEOWNERS

@@ -0,0 +1,38 @@
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+#*       @global-owner1 @global-owner2
+*       @YunBongtae @miloveme
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+#*.js    @js-owner
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+#*.go [email protected]
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+#/build/logs/      @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+#docs/*  [email protected]
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+#apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository.
+#/docs/ @doctocat

.github/ISSUE_TEMPLATE/---bug-report.md

@@ -0,0 +1,27 @@
+---
+name: "\U0001F41C Bug report"
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**How to reproduce**
+Steps to reproduce the behavior:
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Attachments**
+If applicable, add data, logs or screenshots to help explain your problem.
+
+**Environment (please complete the following information)**
+ - caver-js version or git revision that exhibits the issue
+ - OS and its version [e.g. macOS/10.14]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/---enhancement.md

@@ -0,0 +1,20 @@
+---
+name: "\U0001F9E9 Enhancement"
+about: Suggest an improvement idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/--questions-and-others.md

@@ -0,0 +1,11 @@
+---
+name: "❓ Questions and Others"
+about: Questions regarding caver-js or other issues not related to bug nor feature
+  request
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+Freely describe your questions or issues here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,27 @@
+## Proposed changes
+
+- Describe your changes to communicate to the maintainers why we should accept this pull request.
+- If it fixes a bug or resolves a feature request, be sure to link to that issue.
+
+## Types of changes
+
+Please put an x in the boxes related to your change.
+
+- [ ] Bugfix
+- [ ] New feature or enhancement
+- [ ] Others
+
+## Checklist
+
+*Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.*
+
+- [ ] I have read the [CONTRIBUTING](https://github.com/klaytn/caver-js/blob/master/CONTRIBUTING.md) doc
+- [ ] I have signed the [CLA](https://cla-assistant.io/klaytn/caver-js)
+- [ ] Lint and unit tests pass locally with my changes
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have added necessary documentation (if appropriate)
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## Further comments
+
+If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

.gitignore

@@ -0,0 +1,11 @@
+node_modules/
+build/
+dist/
+truffle.js
+/klaytnWallet.iml
+newrelic_agent.log
+logs/
+.vscode/
+
+# env
+.env

CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to Klaytnwallet. As an open source project, Klaytnwallet is always open to the developer community and we welcome your contribution. Please read the guideline below and follow it in all interactions with the project.
+
+## How to Contribute
+
+1. Read this [contributing document](./CONTRIBUTING.md).
+2. Sign [Contributor Licensing Agreement (CLA)](#contributor-license-agreement-cla).
+3. Submit an issue with proper [labeling](#usage-of-labels).
+4. Please wait until the label changes to `contribution welcome` - otherwise, it is not ready to be worked on.
+5. After the label changed to `contribution welcome`, you can start working on the implementation. To avoid any duplicate efforts, it is recommended to update the issue so that other developers see someone working on the issue.
+6. Before making a PR, please make sure you fully tested the code. It is highly recommended to provide the test code as well. After submitting the PR, wait for code review and approval. The reviewer may ask you for additional commits or changes.
+7. Once the change has been approved, the PR is merged by the project moderator.
+8. After merging the PR, we close the pull request. You can then delete the now obsolete branch.
+
+## Types of Contribution
+There are various ways to contribute and participate. Please read the guidelines below regarding the process of each type of contribution.
+
+-   [Issues and Bugs](#issues-and-bugs)
+-   [Feature Requests](#feature-requests)
+-   [Code Contribution](#code-contribution)
+
+### Issues and Bugs
+
+If you find a bug or other issues in Klaytnwallet, please [submit an issue](https://github.com/klaytn/klaytn/issues). Before submitting an issue, please invest some extra time to figure out that:
+
+- The issue is not a duplicate issue.
+- The issue has not been fixed in the latest release of Klaytnwallet.
+Please do not use the issue tracker for personal support requests. Use [email protected] for the personal support requests.
+
+When you report a bug, please make sure that your report has the following information.
+- Steps to reproduce the issue.
+- A clear and complete description of the issue.
+- Code and/or screen captures are highly recommended.
+
+After confirming your report meets the above criteria, [submit the issue](https://github.com/klaytn/klaytnwallet/issues). Please use [labels](#usage-of-labels) to categorize your issue.
+
+### Feature Requests
+
+You can also use the [issue tracker](https://github.com/klaytn/klaytnwallet/issues) to request a new feature or enhancement. Note that any code contribution without an issue link will not be accepted. Please submit an issue explaining your proposal first so that Klaytnwallet community can fully understand and discuss the idea. Please use [labels](#usage-of-labels) for your feature request as well.
+
+#### Usage of Labels
+
+You can use the following labels:
+
+Labels for initial issue categories:
+
+- bug: Issues with the code-level bugs.
+- documentation: Issues with the documentation.
+- enhancement: Issues for enhancement requests.
+
+Status of open issues (will be tagged by the project moderators):
+
+- (no label): The default status.
+- need more information : The issue's creator needs to provide additional information to review.
+- reviewing: The issue is under review.
+- re-label needed: The label needs to be changed to confirmed as being a `bug` or future `enhancement`.
+- approved: The issue is confirmed as being a `bug` to be fixed or `enhancement` to be developed.
+- contribution welcome: The fix or enhancement is approved and you are invited to contribute to it.
+
+Status of closed issues:
+
+- fixed: A fix for the issue was provided.
+- duplicate: The issue is also reported in a different issue and is being managed there.
+- invalid: The issue cannot be reproduced.
+- reject: The issue is rejected after review.
+
+### Code Contribution
+
+Please follow the coding style and quality requirements to satisfy the product standards. You must follow the coding style as best as you can when submitting code. Take note of naming conventions, separation of concerns, and formatting rules.
+
+## Contributor License Agreement (CLA)
+
+Keep in mind when you submit your pull request, you'll need to sign the CLA via [CLA-Assistant](https://cla-assistant.io/klaytn/klaytnwallet) for legal purposes. You will have to sign the CLA just one time, either as an individual or corporation.
+
+You will be prompted to sign the agreement by CLA Assistant (bot) when you open a Pull Request for the first time.

Dockerfile

@@ -0,0 +1,14 @@
+FROM node:10 AS build
+
+# Install dependencies with package.json only, so we can cache node_modules
+# when code changes.
+WORKDIR /build
+COPY package.json .
+RUN npm install
+
+COPY . .
+RUN npm run build:docker
+
+FROM nginx
+COPY --from=build /build/dist /usr/share/nginx/html
+COPY ./config/docker-nginx.conf /etc/nginx/conf.d/default.conf

LICENSE

@@ -0,0 +1,20 @@
+MIT License
+
+Copyright (c) 2018 Klaytn wallet Authors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.