experiment: Tauri v2 migration prototype

.electron-nuxt/config.js

@@ -6,7 +6,7 @@ const SRC_DIR = path.join(PROJECT_ROOT, 'src')
 const config = {
   ELECTRON_RELAUNCH_CODE: 250, // valid range in unix system: <1,255>
   ELECTRON_INSPECTION_PORT: 5858,
-  SERVER_PORT: 9080,
+  SERVER_PORT: 9000,
   SERVER_HOST: 'http://localhost',
 
   PROJECT_ROOT,

.electron-nuxt/renderer/NuxtApp.js

@@ -5,9 +5,6 @@ const { killWithAllSubProcess } = utils
 
 const NUXT_PROCESS_PATH = path.join(__dirname, 'nuxt-process.js')
 
-/**
- * @implements {IStep}
- */
 class NuxtApp {
   constructor(logger) {
     this.logger = logger

.electron-nuxt/renderer/nuxt-process.js

@@ -12,11 +12,7 @@ process.on('message', async ({ action, target }) => {
   }
 
   await nuxt.ready()
-
-  // https://github.com/nuxt/nuxt.js/blob/dev/packages/builder/src/builder.js
   const builder = new Builder(nuxt)
-
-  // https://github.com/nuxt/nuxt.js/blob/dev/packages/generator/src/generator.js
   const generator = new Generator(nuxt, builder)
 
   if (target === 'development') {

.github/CODEOWNERS

@@ -0,0 +1 @@
+@seonglae

.github/FUNDING.yml

@@ -1,5 +1,5 @@
-github:
-  - sungle3737
-custom:
-  - 'https://paypal.me/seonglae'
-  - 'https://www.buymeacoffee.com/seongland'
+github:
+  - seonglae
+custom:
+  - 'https://paypal.me/seonglae'
+  - 'https://www.buymeacoffee.com/seongland'

.github/ISSUE_TEMPLATE/01_bug_report.yml

@@ -0,0 +1,22 @@
+---
+name: 🐛 Bug Report
+description: Something isn't working as expected
+labels:
+  - bug
+body:
+  - type: input
+    id: testcase
+    attributes:
+      label: Reproducible test case
+      description:
+        If possible, please create a minimal test case that reproduces your
+        problem.
+    validations:
+      required: true
+  - type: textarea
+    id: summary
+    attributes:
+      label: Additional information
+      description:
+        Please share any other relevant information not mentioned above. What
+        did you expect to happen? What do you think the problem might be?

.github/ISSUE_TEMPLATE/02_feature_request.yml

@@ -0,0 +1,28 @@
+---
+name: 🟢 Feature Request
+description: Wouldn’t it be nice if
+labels:
+  - feature
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: What?
+      description: Describe your feature idea
+    validations:
+      required: true
+  - type: textarea
+    id: why
+    attributes:
+      label: Why?
+      description: Describe the problem you are facing
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: How?
+      description:
+        Describe you tried or ideas to implement the feature
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/03_others.yml

@@ -0,0 +1,11 @@
+---
+name: Other Issue
+description: Other kind of the issue
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Any precise description of the issue
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/branch-convention.md

@@ -0,0 +1,9 @@
+## Git Branch name Convention
+
+#### TL;DR:
+
+Branch name must be matched by the following regex:
+
+```js
+/^(feature|bug|document|style|refactor|test|deps)\/\#[0-9]{1,5}-[a-z|A-Z|\-|0-9]{1,20}/
+```

.github/commit-convention.md

@@ -0,0 +1,92 @@
+## Git Commit Message Convention
+
+> This is adapted from [Vite's commit convention](https://github.com/vitejs/vite/blob/main/.github/commit-convention.md).
+
+#### TL;DR:
+
+Messages must be matched by the following regex:
+
+<!-- prettier-ignore -->
+```js
+/^(revert: )?(feat|fix|docs|style|refactor|test|ci|cd|build|meta|pr|lint|typing|perf|deps|merge)(\(.+\))?: .{1,50}/
+```
+
+#### Examples
+
+Appears under "Features" header, `dev` subheader:
+
+```
+feat(dev): add 'comments' option
+```
+
+Appears under "Bug Fixes" header, `dev` subheader, with a link to issue #28:
+
+```
+fix(dev): fix dev error
+
+close #28
+```
+
+Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:
+
+```
+perf(build): remove 'foo' option
+
+BREAKING CHANGE: The 'foo' option has been removed.
+```
+
+The following commit and commit `667ecc1` do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header.
+
+```
+revert: feat(compiler): add 'comments' option
+
+This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
+```
+
+### Full Message Format
+
+A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
+
+```
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+### 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.
+
+### Type
+
+If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However, if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
+
+Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
+
+### Scope
+
+The scope could be anything specifying the place of the commit change. For example `dev`, `build`, `workflow`, `cli` etc...
+
+### Subject
+
+The subject contains a succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the 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/pull_request_template.md

@@ -0,0 +1,5 @@
+## Why did you do this
+
+
+## How did you do that
+

.github/renovate.json5

@@ -0,0 +1,14 @@
+{
+  schedule: 'after 12pm on Friday',
+  extends: ['config:base', 'group:allNonMajor'],
+  labels: ['dependencies'],
+  pin: false,
+  rangeStrategy: 'bump',
+  packageRules: [{ depTypeList: ['peerDependencies'], enabled: false }, {
+    "matchPackagePatterns": ["*"],
+    "automerge": true
+  }],
+  dependencyDashboardTitle: "deps: renovate dependency dashboard",
+  branchPrefix: "deps/",
+  commitMessagePrefix: "deps:"
+}

.github/restyled.yml

@@ -0,0 +1,3 @@
+enabled: true
+commit_template: |
+  refactor: restyled by ${restyler.name}

.github/semantic.yml

@@ -8,4 +8,12 @@ types:
   - test
   - ci
   - cd
-  - chore
+  - build
+  - lint
+  - merge
+  - typing
+  - perf
+  - meta
+  - deps
+  - pr
+  - chore

.github/settings.yml

@@ -0,0 +1,6 @@
+repository:
+  has_wiki: false
+  has_projects: false
+  delete_branch_on_merge: true
+  enable_automated_security_fixes: true
+  enable_vulnerability_alerts: true