feat: good first issue

.editorconfig

@@ -0,0 +1,22 @@
+# http://editorconfig.org
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.json]
+insert_final_newline = ignore
+
+[**.min.js]
+indent_style = ignore
+insert_final_newline = ignore
+
+[MakeFile]
+indent_style = tab
+
+[*.md]
+trim_trailing_whitespace = false

.eslintignore

@@ -0,0 +1,4 @@
+node_modules/
+etc/
+build
+/*.json

.eslintrc.json

@@ -0,0 +1,32 @@
+{
+  "env": {
+    "es6": true,
+    "node": true
+  },
+  "extends": [
+    "standard",
+    "plugin:@typescript-eslint/recommended",
+    "prettier/@typescript-eslint",
+    "plugin:prettier/recommended"
+  ],
+  "globals": {
+    "use": true,
+    "Atomics": "readonly",
+    "SharedArrayBuffer": "readonly"
+  },
+  "parserOptions": {
+    "ecmaVersion": 2018
+  },
+  "plugins": ["prettier"],
+  "rules": {
+    "prettier/prettier": "error",
+    "@typescript-eslint/interface-name-prefix": "off",
+    "@typescript-eslint/no-explicit-any": "off",
+    "@typescript-eslint/camelcase": "off"
+  },
+  "settings": {
+    "import/resolver": {
+      "typescript": {}
+    }
+  }
+}

.github/COMMIT_CONVENTION.md

@@ -0,0 +1,70 @@
+## Git Commit Message Convention
+
+> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
+
+Using conventional commit messages, we can automate the process of generating the CHANGELOG file. All commits messages will automatically be validated against the following regex.
+
+``` js
+/^(revert: )?(feat|fix|docs|style|refactor|perf|test|workflow|ci|chore|types|build|improvement)((.+))?: .{1,50}/
+```
+
+## Commit Message Format
+A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
+
+> The **scope** is optional
+
+```
+feat(router): add support for prefix
+
+Prefix makes it easier to append a path to a group of routes
+```
+
+1. `feat` is type.
+2. `router` is scope and is optional
+3. `add support for prefix` is the subject
+4. The **body** is followed by a blank line.
+5. The optional **footer** can be added after the body, followed by a blank line.
+
+## Types
+Only one type can be used at a time and only following types are allowed.
+
+- feat
+- fix
+- docs
+- style
+- refactor
+- perf
+- test
+- workflow
+- ci
+- chore
+- types
+- build
+
+If a type is `feat`, `fix` or `perf`, then the commit will appear in the CHANGELOG.md file. However if there is any BREAKING CHANGE, the commit will always appear in the changelog.
+
+### Revert
+If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>`., where the hash is the SHA of the commit being reverted.
+
+## Scope
+The scope could be anything specifying place of the commit change. For example: `router`, `view`, `querybuilder`, `database`, `model` and so on.
+
+## Subject
+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.
+
+## 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.
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,23 @@
+<!-- CLICK "Preview" FOR INSTRUCTIONS IN A MORE READABLE FORMAT -->
+
+## Prerequisites
+
+We do our best to reply to all the issues on time. If you will follow the given guidelines, the turn around time will be faster.
+
+- Ensure the issue isn't already reported.
+- Ensure you are reporting the bug in the correct repo.
+
+*Delete the above section and the instructions in the sections below before submitting*
+
+## Description
+
+If this is a feature request, explain why it should be added. Specific use-cases are best.
+
+For bug reports, please provide as much *relevant* info as possible.
+
+## Package version
+<!-- YOUR ANSWER -->
+
+## Error Message & Stack Trace
+
+## Relevant Information

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+<!-- CLICK "Preview" FOR INSTRUCTIONS IN A MORE READABLE FORMAT -->
+
+## Proposed changes
+
+Describe the big picture of your changes here 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
+
+What types of changes does your code introduce?
+
+_Put an `x` in the boxes that apply_
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+## 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/rana-express/rana-wallet/blob/plugin-macro-response.git/CONTRIBUTING.md) doc
+- [ ] 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)
+
+## 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...

.github/workflows/lint.yml

@@ -0,0 +1,36 @@
+on: [pull_request]
+
+name: Check TSLint
+
+jobs:
+  build:
+    runs-on: ubuntu-18.04
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v2
+
+      - name: Setup NodeJs
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          always-auth: false
+          scope: dedsec
+
+      - name: Yarn intall
+        run: yarn install
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}
+
+      - name: Try linting
+        run: yarn lint:fix
+
+      - name: Init testing
+        run: yarn ci-test
+
+      - name: Build
+        run: yarn build
+
+        env:
+          CI: true

.github/workflows/publish.yml

@@ -0,0 +1,24 @@
+
+name: Publish Package
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  build:
+
+    runs-on: ubuntu-18.04
+
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-node@v1
+      with:
+        node-version: '13.x'
+        registry-url: 'https://npm.pkg.github.com'
+    - run: yarn
+    - run: yarn publish
+      env:
+        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        name: Deploy

.gitignore

@@ -0,0 +1,13 @@
+node_modules
+coverage
+.DS_STORE
+.nyc_output
+.idea
+.vscode/
+*.sublime-project
+*.sublime-workspace
+*.log
+build
+dist
+shrinkwrap.yaml
+package-lock.json

.npmignore

@@ -0,0 +1,5 @@
+*
+!build/**/**/*
+build/**/*.test.*
+!package.json
+!*.md

.nycrc

@@ -0,0 +1,20 @@
+{
+  "cache": false,
+  "exclude": [
+    "build",
+    "test"
+  ],
+  "extension": [
+    ".ts"
+  ],
+  "report-dir": "./test/coverage",
+  "temp-dir": "./test/coverage/.nyc_output",
+  "reporter": [
+    "text-summary",
+    "html"
+  ],
+  "branches": 30,
+  "lines": 30,
+  "functions": 30,
+  "statements": 30
+}

.prettierrc

@@ -0,0 +1,7 @@
+{
+  "singleQuote": true,
+  "trailingComma": "all",
+  "arrowParens": "avoid",
+  "endOfLine": "lf",
+  "semi": false
+}

.yarnrc

@@ -0,0 +1 @@
+"@secjs:registry" "https://npm.pkg.github.com"

CONTRIBUTING.md

@@ -0,0 +1,39 @@
+# Contributing
+
+We love pull requests. And following this guidelines will make your pull request easier to merge
+
+## Prerequisites
+
+- Install [EditorConfig](http://editorconfig.org/) plugin for your code editor to make sure it uses correct settings.
+- Fork the repository and clone your fork.
+- Install dependencies: `npm install`.
+
+## Coding style
+
+We make use of Typescript along with [Tslint](https://palantir.github.io/tslint) to ensure a consistent coding style. All of the rules are defined inside the `tslint.json` file.
+
+## Development work-flow
+
+Always make sure to lint and test your code before pushing it to the GitHub.
+
+```bash
+npm test
+```
+
+Just lint the code
+
+```bash
+npm run lint
+```
+
+**Make sure you add sufficient tests for the change**.
+
+## Other notes
+
+- Do not change version number inside the `package.json` file.
+- Do not update `CHANGELOG.md` file.
+- Do not update `tslint.json` or `tslint.js` file. If something prevents you writing code, please create an issue for same.
+
+## Need help?
+
+Feel free to ask.

README.md

@@ -1,2 +1,47 @@
-# Exceptions
-Simple Exceptions for NodeJS Application
+# Exceptions 📦
+
+> Very simple Exceptions for NodeJS Application
+
+<p>
+  <img alt="GitHub language count" src="https://img.shields.io/github/languages/count/secjs/exceptions?style=for-the-badge&logo=appveyor">
+
+  <img alt="Repository size" src="https://img.shields.io/github/repo-size/secjs/exceptions?style=for-the-badge&logo=appveyor">
+
+  <img alt="License" src="https://img.shields.io/badge/license-MIT-brightgreen?style=for-the-badge&logo=appveyor">
+</p>
+
+The intention behind this repository is to always maintain a viable and simple Exceptions handler to use in any type of `NodeJS Framework`
+
+<img src=".github/exceptions.jpg" width="200px" align="right" hspace="30px" vspace="100px">
+
+## Installation
+
+To use Exceptions in your project, first you need to install `@SecJS/Responses`
+
+```bash
+yarn add @SecJS/Responses
+```
+
+Then you can install the Exceptions using;
+
+```bash
+yarn add @SecJS/Exceptions
+```
+
+## Usage
+
+> You can call the any of Exceptions classes to create a new error
+
+```js
+import {
+  InternalErrorException,
+  InvalidArgsExceptions,
+  NotFoundException,
+  UnauthorizedException
+} from '@SecJS/Exceptions'
+
+if (1+1 = 3) {
+  throw new InternalErrorException('1+1 is not 3!!', 'INTERNAL_ERROR')
+}
+
+```

config.json

@@ -0,0 +1,7 @@
+{
+  "core": false,
+  "ts": true,
+  "license": "Unlicense",
+  "services": [],
+  "minNodeVersion": "10.15.3"
+}