chore: initial commit

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

chore: wip

Author: chrisbbreuer

.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

.gitattributes

@@ -0,0 +1 @@
+* text=auto

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at <chris@stacksjs.org>. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

.github/CONTRIBUTING.md

@@ -0,0 +1,192 @@
+# Contributing
+
+WIP: Updates to here are in progress.
+
+First off, thank you for taking the time to contribute to the Stacks ecosystem ❤️
+
+> **Note**
+> The likelihood is high that the repo you are working on is either a Stack or Stacks itself. In both cases, you will be exposed to a meshup of technologies, like [Vite][vite], [Tauri][tauri], [Nitro][nitro], [Vue][vue], and [Bun][bun].
+
+## 💭 Knowledge
+
+### TypeScript
+
+It's important to note early on that these projects are written with [TypeScript][typescript]. If you're unfamiliar with it (or any strongly typed languages such as Java) then this may feel like a slight roadblock. However, there's never a truly perfect time to start learning it, so ... why not today using well-written codebases as your playground?
+
+_Don't be discouraged. You will get by learning TypeScript on-the-fly as you review some of the examples within the codebase. It's easy to get started—the code is, we hope, very approachable (and readable)._
+
+### Architecture
+
+An understanding of the framework architecture and design will help if you're looking to contribute long-term, or if you are working on a "more complex" PR. Browse the source and read our documentation to get a better sense of how it is structured. The documentation is very thorough and can be used as your progressive guide as you're learning more about Stacks.
+
+Feel free to ask any question _(Twitter, Discord, or GitHub Discussions)_, we would love to elaborate & collaborate.
+
+### Stacks/Core Setup
+
+Are you interested in contributing to the Stacks codebase?
+
+**Working on your first Pull Request?** You can learn how from this free series [How to Contribute to an Open Source Project on GitHub][pr-beginner-series].
+
+Head over to the [repository][stacks] on GitHub and click the Fork button in the top right corner. After the project has been forked, run the following commands in your terminal:
+
+```bash
+# Replace {github-username} with your GitHub username.
+git clone https://github.com/{github-username}/stacks --depth=1
+
+cd stacks
+
+# Create a branch for your PR, replace {issue-no} with the GitHub issue number.
+git checkout -b issue-{issue-no}
+```
+
+Now it'll help if we keep our `main` branch pointing at the original repository and make
+pull requests from the forked branch.
+
+```bash
+# Add the original repository as a "remote" called "upstream".
+git remote add upstream git@github.com:stacksjs/stacks.git
+
+# Fetch the git information from the remote.
+git fetch upstream
+
+# Set your local main branch to use the upstream main branch whenever you run `git pull`.
+git branch --set-upstream-to=upstream/main main
+
+# Run this when we want to update our version of main.
+git pull
+```
+
+_You may also use GitHub Desktop or any other GUI—if that is your preference._
+
+### Buddy Toolkit
+
+The following list of commands is one of the most common ways to interact with the Stacks API. Meet Buddy:
+
+```bash
+buddy install # installs all dependencies
+buddy dev # starts one of the dev servers (components, functions, views, desktop or docs)
+buddy build # follow CLI prompts to select which library (or server) to build
+buddy commit # follow CLI prompts for committing changes
+buddy release # creates the releases of the stack & consequently, publishes them (to npm)
+buddy upgrade # auto-update deps & the Stacks framework
+
+buddy make:component HelloWorld # scaffolds a component
+buddy make:function HelloWorld # scaffolds a function
+buddy make:view hello-world # scaffolds a page (https://my-project.test/hello-world)
+
+buddy help
+```
+
+<details>
+<summary>View the complete Buddy Toolkit</summary>
+
+```bash
+buddy --help # view help menu
+buddy install # installs your dependencies
+buddy fresh # fresh reinstall of all deps
+buddy update # auto-update deps & the Stacks framework
+
+buddy --version # get the Stacks version
+buddy --help # view help menu
+
+# if you need any more info to any command listed here, you may suffix
+# any of them via the "help option", i.e. `buddy command --help`
+
+buddy dev # starts one of the dev servers (components, functions, views, or docs)
+buddy dev:components # starts local playground dev server
+buddy dev:desktop # starts the Desktop playground
+buddy dev:views # starts local playground views dev server
+buddy dev:functions # stubs local the functions
+buddy dev:docs # starts local docs dev server
+
+# for Laravel folks, `serve` may ring more familiar than the `dev` name. Hence, we aliased it:
+buddy serve # starts one of the dev servers (components, functions, viewsviews, or docs)
+buddy serve:components # starts local playground dev server
+buddy serve:views # starts local playground views dev server
+buddy serve:functions # stubs local the functions
+buddy serve:docs # starts local docs dev server
+
+# sets your application key
+buddy key:generate
+
+buddy make:stack project
+buddy make:component HelloWorld
+buddy make:function hello-world
+buddy make:view hello-world
+buddy make:lang de
+buddy make:database cars
+buddy make:table brands
+buddy make:migration create_cars_table
+buddy make:factory cars
+
+buddy lint # runs linter
+buddy lint:fix # runs linter and fixes issues
+
+buddy commit # follow CLI prompts for committing staged changes
+buddy release # creates the releases for the stack & triggers the Release Action (workflow)
+buddy changelog # generates CHANGELOG.md
+
+# building for production (e.g. npm, Vercel, Netlify, et al.)
+buddy build # select a specific build (follow CLI prompts)
+buddy build:components # builds Vue component library & Web Component library
+buddy build:functions # builds function library
+buddy build:vue-components # builds Vue 2 & 3-ready Component library
+buddy build:web-components # builds framework agnostic Web Component library (i.e. Custom Elements)
+buddy build:views # builds views
+
+# when deploying your app/s
+buddy deploy:docs
+buddy deploy:functions
+buddy deploy:views
+
+# select the example to run (follow CLI prompts)
+buddy example
+
+# test your stack
+buddy test # runs test suite (unit & e2e)
+buddy test:coverage # runs test coverage
+buddy test:types # runs typecheck
+```
+
+</details>
+
+## 🧪 Testing
+
+All the framework tests are stored within the `./storage/framework/tests` project folder. When adding or updating functionality, please ensure it is covered through our test suite. Ensure so by running `buddy test`.
+
+When working on an individual Stack, tests are stored within the `./tests` project folder & it is recommended to write tests (when useful). Bu
+
+## ✍️ Commit
+
+Stacks uses [semantic commit messages][semantic-commit-style] to automate package releases. No worries, you may not be aware what this is or how it works—just let Buddy guide you.  Stacks automated the commit process for you, simply run `buddy commit` in your terminal and follow the instructions.
+
+For example,
+
+```bash
+# Add all changes to staging to be committed.
+git add .
+
+# Commit changes.
+buddy commit
+
+# Push changes up to GitHub.
+git push
+```
+
+_By following these minor steps, Stacks is able to automatically release new versions & generate relating local & remote changelogs._
+
+## 🎉 Pull Request
+
+When you're all done, head over to the [repository][stacks], and click the big green `Compare & Pull Request` button that should appear after you've pushed changes to your fork.
+
+Don't expect your PR to be accepted immediately or even accepted at all. Give the community time to vet it and see if it should be merged. Please don't be disheartened if it’s not accepted. Your contribution is appreciated more than you can imagine, and even a unmerged PR can teach us a lot ❤️
+
+[typescript]: https://www.typescriptlang.org
+[vue]: https://vuejs.org/
+[vite]: https://vitejs.dev/
+[tauri]: https://tauri.app/
+[nitro]: https://nitro.unjs.io/
+[bun]: https://bun.sh/
+[stacks]: https://github.com/stacksjs/stacks
+[semantic-commit-style]: https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716
+[pr-beginner-series]: https://app.egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github

.github/EXPLANATIONS.md

@@ -0,0 +1,41 @@
+# CI/CD Configurations
+
+This folder contains GitHub configurations for the project, including the following features:
+
+- GitHub Actions (./workflows)
+  - [CI][CI] - all CI jobs for the project
+    - Lints the code
+    - `typecheck`s the code
+    - Auto fixes & applies code style updates via a PR
+    - Runs tests (unit & end-to-end)
+    - Runs on `ubuntu-latest` with `bun-versions` set to `[x]`
+  - [Release][Release] - automates the release process & changelog generation
+- [Stale][Stale] - Automates managing stale GitHub issues
+- Renovate
+  - automatically updates all the dependencies listed in all package.json files throughout the monorepo
+
+Aside from these implemented features, this folder also contains the issue templates used to create new GitHub issues.
+
+## 🚜 Contributing
+
+Please review the [Contributing Guide](https://github.com/stacksjs/contributing) for details.
+
+## 🏝 Community
+
+For help, discussion about best practices, or any other conversation that would benefit from being searchable:
+
+[Discussions on GitHub](https://github.com/stacksjs/stacks/discussions)
+
+For casual chit-chat with others using this package:
+
+[Join the Stacks Discord Server](https://discord.gg/stacksjs)
+
+## 📄 License
+
+The MIT License (MIT). Please see [LICENSE](../LICENSE.md) for more information.
+
+Made with 💙
+
+[CI]: ./workflows/ci.yml
+[Release]: ./workflows/release.yml
+[Stale]: ./stale.yml

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: [stacksjs, chrisbbreuer]
+open_collective: stacksjs

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,49 @@
+name: 🐞 Bug report
+description: Report an issue
+labels: [pending triage]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is. If you intend to submit a PR for this issue, tell us in the description. Thanks!
+      placeholder: Bug description
+    validations:
+      required: true
+  - type: input
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: A [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) is **required**, otherwise the issue might be closed without further notice. [**Why & How?**](https://antfu.me/posts/why-reproductions-are-required)
+      placeholder: Reproduction
+    validations:
+      required: true
+  - type: textarea
+    id: system-info
+    attributes:
+      label: System Info
+      description: Output of `bunx envinfo --system --binaries --browsers`
+      render: Shell
+      placeholder: System, Binaries, Browsers
+    validations:
+      required: true
+  - type: checkboxes
+    id: checkboxes
+    attributes:
+      label: Validations
+      description: Before submitting the issue, please make sure you do the following
+      options:
+        - label: Follow our [Code of Conduct](https://github.com/stacksjs/.github/blob/main/CODE_OF_CONDUCT.md)
+          required: true
+        - label: Read the [Contributing Guide](https://github.com/stacksjs/contributing).
+          required: true
+        - label: Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
+          required: true
+        - label: Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
+          required: true
+        - label: The provided reproduction is a [minimal reproducible](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,10 @@
+contact_links:
+  - name: 🙌 Contribution Guide
+    url: https://github.com/stacksjs/contribute
+    about: Please read through before making contributions.
+  - name: 💬 Stacks Discord Server
+    url: https://discord.gg/stacksjs/
+    about: Want to discuss / chat with the community? Here you go!
+  - name: ⁉️ Why & how to create a reproduction?
+    url: https://antfu.me/posts/why-reproductions-are-required
+    about: A reproduction is very important for maintainers to help on your issues!