Merge pull request #24 from svelte-plugins/updates

refactor(repo): update tooling and cleaning up builds

Author: dysfunc

.eslintignore

@@ -0,0 +1,3 @@
+node_modules
+src/**/*.snap.js
+.eslintrc.json

.eslintrc.json

@@ -0,0 +1,28 @@
+{
+  "env": {
+    "es2017": true,
+    "commonjs": true,
+    "node": true
+  },
+  "parserOptions": {
+    "ecmaVersion": 2020,
+    "sourceType": "module"
+  },
+  "plugins": ["vitest"],
+  "extends": ["eslint:recommended", "plugin:vitest/recommended"],
+  "ignorePatterns": ["**/*.snap.js"],
+  "overrides": [
+    {
+      "files": ["*.svelte"],
+      "parser": "svelte-eslint-parser"
+    }
+  ],
+  "rules": {
+    "eqeqeq": "error",
+    "no-useless-escape": "off",
+    "no-unused-expressions": "off",
+    "no-unused-vars": "off",
+    "no-self-assign": "off",
+    "no-undef": "off"
+  }
+}

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @dysfunc

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Report a bug to help us improve the overall user experience
+title: '🐛 '
+labels: 'Type: Bug'
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest a new feature or functionality enhancement
+title: '✨ '
+labels: 'Type: Feature'
+assignees: ''
+---
+
+**Is your feature 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/issue-template.md

@@ -0,0 +1,7 @@
+---
+name: Issue
+about: Track a new feature, enhancement, or general task.
+title: ''
+labels: ''
+assignees: ''
+---

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,37 @@
+**Why these changes?**
+
+**How do we test?**
+
+**Screenshots**
+
+<!--
+# Instructions:
+1. Choose an emoji to categorize your pull request (copy-paste emoji in front of your title):
+  ✨ New feature
+  🐛 Bugfix
+  🔥 P0 fix
+  🧪 Tests
+  🚀 Performance improvements
+  🖍 Styling
+  ♿ Accessibility
+  🌐 Internationalization
+  📖 Documentation
+  🏗 Infrastructure / Tooling / Builds / CI
+  ⏪ Reverting a previous change
+  🧹 Code refactors and general housekeeping
+  🗑️ Code removal
+
+2. Pick a meaningful title for your pull request!
+  - Use sentence case. Keep it short. ex: `✨ Released manage users list view`
+3. Enter a succinct description that says why the PR is necessary, and what it does.
+  Examples of good descriptions:
+  - Implement aspect of X
+  - Leave out feature Y because of A
+  - Improve performance by B
+  - Improve accessibility by C
+4. If the pull request addresses an issue, mention it with keywords `Fixes`, `Closes`, or `Resolves`.
+  - Using one of the above keywords will automatically close the issue (ex: Fixes #17)
+5. Make sure to assign the appropriate label(s) to the pull request!
+6. Provide clear testing instructions that include any pertinent information, i.e. roles, feature flags, etc.)
+7. Include screenshots of your changes if they impact the UI (Before & After).
+-->

.github/workflows/unit.yml

@@ -0,0 +1,37 @@
+name: Unit Tests (Vitest)
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    if: |
+      (
+        !contains(github.event.head_commit.message, '[skip ci]') &&
+        !contains(github.event.head_commit.message, 'version bump')
+      )
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '18'
+          registry-url: 'https://registry.npmjs.org'
+      - uses: szenius/[email protected]
+        with:
+          timezoneLinux: "America/Los_Angeles"
+          timezoneMacos: "America/Los_Angeles"
+          timezoneWindows: "Pacific Standard Time"
+      - run: npm i
+      - run: npm test
+
+      - uses: actions/upload-artifact@v2
+        if: failure()
+        with:
+          name: unit-tests
+          path: ${{ github.workspace }}/coverage/
+          retention-days: 5

.gitignore

@@ -2,6 +2,7 @@
 
 # except
 !.editorconfig
+!.eslintignore
 !.eslintrc.json
 !.github
 !.gitignore
@@ -20,7 +21,6 @@
 # generated
 .vercel
 /node_modules
-/lib
 /dist
 
 # testing

.lintstagedrc

@@ -1,3 +1,6 @@
 {
-  "./src/**/*.{test.js,js,svelte}": ["eslint -c ./.eslintrc.js --fix", "prettier --write"]
+  "./src/**/*.{test.js,js,json,svelte}": [
+    "eslint -c ./.eslintrc.json --fix",
+    "prettier --write"
+  ]
 }