chore: reset after messing up

Author: ndabAP

.browserslistrc

@@ -0,0 +1,3 @@
+> 1%
+last 2 versions
+not ie <= 8

.editorconfig

@@ -0,0 +1,5 @@
+[*.{js,jsx,ts,tsx,vue}]
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true
+insert_final_newline = true

.eslintignore

@@ -0,0 +1 @@
+./dist

.eslintrc.js

@@ -0,0 +1,35 @@
+module.exports = {
+  root: true,
+  env: {
+    node: true,
+    jest: true
+  },
+
+  extends: [
+    'plugin:vue/essential',
+    '@vue/standard'
+  ],
+
+  rules: {
+    'no-console': process.env.NODE_ENV === 'production' ? 'error' : 'off',
+    'no-debugger': process.env.NODE_ENV === 'production' ? 'error' : 'off',
+    'vue/html-closing-bracket-newline': ['error', {
+      singleline: 'never',
+      multiline: 'never'
+    }],
+
+    'vue/max-attributes-per-line': ['error', {
+      singleline: 1,
+      multiline: 1
+    }],
+
+    'vue/attributes-order': 'error',
+    'vue/order-in-components': 'error',
+    'vue/html-indent': 'error',
+    quotes: ['error', 'single']
+  },
+
+  parserOptions: {
+    parser: 'babel-eslint'
+  }
+}

.github/workflows/publish.yml

@@ -0,0 +1,40 @@
+name: Test, publish
+
+on: [push, pull_request]
+
+jobs:
+  test:
+    name: Test
+    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12'
+      - name: Lint
+        run: |
+          npm i
+          npm run lint
+      - name: Test
+        run: |
+          npm i
+          npm run test
+  
+  publish:
+    name: Publish
+    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
+    runs-on: ubuntu-latest
+    needs: [test]
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12'
+      - name: Publish
+        run: npm i && npm run build:lib && npx semantic-release
+        env:
+          GH_TOKEN: ${{ secrets.GH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/test.yml

@@ -0,0 +1,25 @@
+name: Test
+
+on: [push, pull_request]
+
+jobs:
+  test:
+    name: Test
+    if: github.event_name == 'push' && github.ref != 'refs/heads/master'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12'
+      
+      - name: Lint
+        run: |
+          npm i
+          npm run lint
+
+      - name: Test
+        run: |
+          npm i
+          npm run test

.gitignore

@@ -0,0 +1,24 @@
+.DS_Store
+node_modules
+
+# build files
+dist
+
+# local env files
+.env.local
+.env.*.local
+
+# Log files
+npm-debug.log*
+
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw*
+
+# Jest files
+coverage

CHANGELOG.md

@@ -0,0 +1,10 @@
+## 1.0.0 (2020-09-01)
+
+
+### ⚠ BREAKING CHANGES
+
+* add missing stdout parameter
+
+### Documentation
+
+* add missing stdout parameter ([75c6799](https://github.com/ndabAP/vue-command/commit/75c679940d875c49939542ee3fa1a0bbcae14158))

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contributing
+
+I'm happy you want to contribute. Please make sure you read and fulfil the following sections.
+
+## General
+
+- Use [JavaScript Standard Style](https://standardjs.com/)
+- Watch for a clean and readable code style. More [here](https://medium.com/javascript-scene/elements-of-javascript-style-caa8821cb99f)
+- Don't be afraid of new JavaScript features
+- Edit or add tests if appropriate
+
+## Commits
+
+You must follow the [conventional commits schema](https://github.com/conventional-changelog/commitlint/tree/master/@commitlint/config-conventional). Commits are linted and will fail if not following the schema so. This helps to be consistent across developers and makes [semantic release](https://github.com/semantic-release/semantic-release) possible.
+
+If you change the `README.md`, use `docs!` to trigger a breaking change (increases major version) to make the change visible at npmjs.com.
+
+## Build and release
+
+You don't need to take care of any library building when you are finished. Releases are done automatically by [semantic-release](https://github.com/semantic-release/semantic-release). You must follow the given commit schema (see [Commits section](#commits)) to trigger an automatic release with the correct versioning.