first commit

Author: kazupon

.editorconfig

@@ -0,0 +1,9 @@
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true

.eslintignore

@@ -0,0 +1,3 @@
+./lib
+./jest.config.js
+./test/fixtures

.eslintrc.js

@@ -0,0 +1,32 @@
+'use strict'
+
+module.exports = {
+  root: true,
+  globals: {},
+  env: {
+    node: true,
+    jest: true
+  },
+  extends: [
+    'plugin:vue-libs/recommended',
+    'plugin:@typescript-eslint/recommended',
+    'plugin:@typescript-eslint/eslint-recommended',
+    'prettier/@typescript-eslint',
+    'plugin:prettier/recommended'
+  ],
+  plugins: ['@typescript-eslint'],
+  parser: 'vue-eslint-parser',
+  parserOptions: {
+    parser: '@typescript-eslint/parser',
+    sourceType: 'module'
+  },
+  rules: {
+    'object-curly-spacing': 'off',
+    '@typescript-eslint/explicit-function-return-type': 'off',
+    '@typescript-eslint/member-delimiter-style': 'off',
+    '@typescript-eslint/no-use-before-define': 'off',
+    '@typescript-eslint/explicit-module-boundary-types': 'off',
+    '@typescript-eslint/ban-ts-comment': 'off',
+    '@typescript-eslint/no-non-null-assertion': 'off'
+  }
+}

.gitattributes

@@ -0,0 +1 @@
+*.json  linguist-language=JSON-with-Comments

.github/CONTRIBUTING.md

@@ -0,0 +1,62 @@
+# @intlify/cli Contributing Guide
+
+- [Issue Reporting Guidelines](#issue-reporting-guidelines)
+- [Pull Request Guidelines](#pull-request-guidelines)
+- [Development Setup](#development-setup)
+
+## Issue Reporting Guidelines
+
+- The issue list of this repo is **exclusively** for bug reports and feature requests. Non-conforming issues will be closed immediately.
+
+- Try to search for your issue, it may have already been answered or even fixed in the main branch.
+
+- Check if the issue is reproducible with the latest stable version of @intlify/cli. If you are using a pre-release, please indicate the specific version you are using.
+
+- It is **required** that you clearly describe the steps necessary to reproduce the issue you are running into. Issues with no clear repro steps will not be triaged. If an issue labeled `Status: Need More Info` receives no further input from the issue author for more than 5 days, it will be closed.
+
+- For bugs that involves build setups, you can create a reproduction repository with steps in the README.
+
+- If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.
+
+## Pull Request Guidelines
+
+- Checkout a topic branch from the `main` branch.
+
+- It's OK to have multiple small commits as you work on the PR - we will let GitHub automatically squash it before merging.
+
+- Make sure `npm test` passes. (see [development setup](#development-setup))
+
+- If adding new feature:
+  - Add accompanying test case.
+  - Provide convincing reason to add this feature. Ideally you should open a suggestion issue first and have it greenlighted before working on it.
+
+- If fixing a bug:
+  - Provide detailed description of the bug in the PR.
+  - Add appropriate test coverage if applicable.
+
+### Work Step Example
+- Fork the repository from [@intlify/cli](https://github.com/intlify/cli) !
+- Create your topic branch from `main`: `git branch my-new-topic origin/main`
+- Add codes and pass tests !
+- Commit your changes: `git commit -am 'Add some topic'`
+- Push to the branch: `git push origin my-new-topic`
+- Submit a pull request to `main` branch of `intlify/api-docs-gen` repository !
+
+## Development Setup
+
+After cloning the repo, run:
+
+    $ npm install
+
+### Commonly used NPM scripts
+
+    # lint source codes
+    $ npm run lint
+
+    # run the full test suite, include linting
+    $ npm test
+
+There are some other scripts available in the `scripts` section of the `package.json` file.
+
+The default test script will do the following: lint with ESLint -> unit tests with coverage. **Please make sure to have this pass successfully before submitting a PR.** Although the same tests will be run against your PR on the CI server, it is better to have it working locally beforehand.
+

.github/FUNDING.yml

@@ -0,0 +1,9 @@
+# These are supported funding model platforms
+
+github: kazupon
+patreon: # 
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+issuehunt: # 
+custom: # Replace with a single custom sponsorship URL

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,28 @@
+name: Test
+on:
+  push:
+    branches-ignore:
+      - gh-pages
+  pull_request:
+env:
+  CI: true
+
+jobs:
+  test:
+    name: "Test on Node.js ${{ matrix.node }} OS: ${{matrix.os}}"
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node: [10, 12, 14]
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+      - name: Setup Node.js ${{ matrix.node }}
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node }}
+      - name: Install
+        run: yarn install
+      - name: Test
+        run: yarn test

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+coverage
+node_modules
+.DS_Store
+lib
+*.log
+*.swp
+*~
+temp