feat!: rebuilt using reusable code from agent project

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Something is occurring that I think is wrong
+title: ''
+labels: "\U0001F41B bug"
+assignees: ''
+
+---
+
+## What is the current behavior?
+
+> What's happening that seems wrong?
+
+## Steps to reproduce
+
+> To make it faster to diagnose the root problem. Tell us how can we reproduce the bug.
+
+## Expected behavior
+
+> What would you expect to happen when following the steps above?
+
+## Please tell us about your environment
+
+> We want to make sure the problem isn't specific to your operating system or programming language.
+  
+- **Operating System/Version:** Windows 10
+- **Language:** [all | TypeScript | Python | PHP | etc]
+- **Browser:** Chrome
+
+## Other information
+
+> Anything else we should know? (e.g. detailed explanation, stack-traces, related issues, suggestions how to fix, links for us to have context, eg. stack overflow, codepen, etc)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,6 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Deepgram Developer Community
+    url: https://github.com/orgs/deepgram/discussions
+  - name: Deepgram on Twitter
+    url: https://twitter.com/DeepgramAI

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,24 @@
+---
+name: Feature Request
+about: I think X would be a cool addition or change.
+title: ''
+labels: "✨ enhancement"
+assignees: ''
+
+---
+
+## Proposed changes
+
+> Provide a detailed description of the change or addition you are proposing
+
+## Context
+
+> Why is this change important to you? How would you use it? How can it benefit other users?
+
+## Possible Implementation
+
+> Not obligatory, but suggest an idea for implementing addition or change
+
+## Other information
+
+> Anything else we should know? (e.g. detailed explanation, related issues, links for us to have context, eg. stack overflow, codepen, etc)

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,27 @@
+## Proposed changes
+
+Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
+
+## Types of changes
+
+What types of changes does your code introduce to the Vonage for Visual Studio Code extension?
+_Put an `x` in the boxes that apply_
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update or tests (if none of the other choices apply)
+
+## Checklist
+
+_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._
+
+- [ ] I have read the [CONTRIBUTING](../../CONTRIBUTING.md) doc
+- [ ] Lint and unit tests pass locally with my changes
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have added necessary documentation (if appropriate)
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## Further comments
+
+If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

.github/dependabot.yml

@@ -0,0 +1,12 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for more information:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+# https://containers.dev/guide/dependabot
+
+version: 2
+updates:
+ - package-ecosystem: "devcontainers"
+   directory: "/"
+   schedule:
+     interval: weekly

.github/workflows/release.yml

@@ -0,0 +1,39 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+      - "next/**"
+      - "rc/**"
+      - "beta/**"
+      - "alpha/**"
+  workflow_dispatch:
+
+jobs:
+  release:
+    name: Release / Node ${{ matrix.node }}
+    strategy:
+      matrix:
+        node: ["20"]
+
+    runs-on: ubuntu-latest
+
+    permissions:
+      contents: write
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up Node
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node }}
+
+      - run: |
+          npm ci
+
+      - name: Create a release
+        run: npx semantic-release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_PUSH_TOKEN }}

.gitignore

@@ -34,3 +34,16 @@ yarn-error.log*
 # typescript
 *.tsbuildinfo
 next-env.d.ts
+
+
+# Contentlayer
+.contentlayer
+
+# vscode
+.vscode
+
+# container
+.devcontainer
+
+# pycharm
+.idea

.releaserc.json

@@ -0,0 +1,34 @@
+{
+  "branches": [
+    { "name": "main" },
+    { "name": "next", "channel": "next", "prerelease": true },
+    { "name": "rc", "channel": "rc", "prerelease": true },
+    { "name": "beta", "channel": "beta", "prerelease": true },
+    { "name": "alpha", "channel": "alpha", "prerelease": true }
+  ],
+  "tagFormat": "${version}",
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    [
+      "@semantic-release/npm",
+      {
+        "npmPublish": false
+      }
+    ],
+    [
+      "@semantic-release/changelog",
+      {
+        "changelogFile": "CHANGELOG.md",
+        "changelogTitle": "Change Log"
+      }
+    ],
+    [
+      "@semantic-release/git",
+      {
+        "assets": ["package.json", "CHANGELOG.md"]
+      }
+    ],
+    "@semantic-release/github"
+  ]
+}

CHANGELOG.md

@@ -0,0 +1 @@
+Change Log

CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Code of Conduct
+
+The Deepgram developer community is filled with amazing, clever and creative people, and we're excited for you to join us. Our goal is to create safe and inclusive spaces, have meaningful conversations, and explore ways to make sure that every voice is heard and understood.
+
+#### Being a Good Community Member
+
+Because we prioritize creating a safe space for our members, we believe in actively working on how we, as individuals, can ensure a positive community environment through our own actions and mindsets.
+
+Every supportive community starts with each member. We feel it’s important to be open to others, respectful, and supportive. As part of the Deepgram community, please begin by thinking carefully about and agreeing with the following statements:
+
+- I will be welcoming to everyone at the table;
+- I will be patient and open to learning from everyone around me;
+- I will treat everyone with respect, because they deserve it;
+- I will be mindful of the needs and boundaries of others;
+
+We strive to create a space where we learn and grow together. Here are some other key things you can do to make the community great:
+
+### BE HUMBLE
+
+People come from all different places, and it’s best not to make assumptions about what they think or feel. Approach others with curiosity and openness. We **all** have a lot to learn from each other.
+
+### BE HELPFUL
+
+If someone asks for help, consider jumping in. You don’t have to be an expert to talk through a problem, suggest a resource, or help find a solution. We all have something to contribute.
+
+### ENCOURAGE OTHERS
+
+There’s no one path to have a career in technology or to this community. Let’s engage others in ways that create opportunities for learning and fun for all of us.
+
+## Our Pledge
+
+Everyone who participates in our community must agree to abide by our Code of Conduct. By agreeing, you help create a welcoming, respectful, and friendly community based on respect and trust. We are committed to creating a harassment-free community.
+
+These rules will be strictly enforced in any and all of our official spaces, including direct messages, social media, and physical and virtual events. Everyone who participates in these spaces is required to agree to this community code. We also ask and expect community members to observe these rules anywhere the community is meeting (for example, online chats on unofficial platforms or event after-parties).
+
+## Our Standards
+
+### BE RESPECTFUL
+
+Exercise consideration and respect in your speech and actions. Be willing to accept and give feedback gracefully.
+
+Don’t make offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, ethnicity, immigration status, religion, experience level, socioeconomic status, nationality, or other identity markers.
+
+Additionally, don’t insult or demean others. This includes making unwelcome comments about a person’s lifestyle choices and practices, including things related to diet, health, parenting, drugs, or employment. It’s not okay to insult or demean others if it’s "just a joke."
+
+### BE WELCOMING AND OPEN
+
+Encourage others, be supportive and willing to listen, and be willing to learn from others’ perspectives and experiences. Lead with empathy and kindness.
+
+Don’t engage in gatekeeping behaviors, like questioning the intelligence or knowledge of others as a way to prove their credentials. And don’t exclude people for prejudicial reasons.
+
+### RESPECT PRIVACY
+
+Do not publish private communications without consent. Additionally, never disclose private aspects of a person’s personal identity without consent, except as necessary to protect them from intentional abuse.
+
+### RESPECT PERSONAL BOUNDARIES
+
+Do not introduce gratuitous or off-topic sexual images, languages, or behavior in spaces where they are not appropriate. Never make physical contact or simulated physical contact without consent or after a request to stop. Additionally, do not continue to message others about anything if they ask you to stop or leave them alone.
+
+#### BE A GOOD NEIGHBOR
+
+Contribute to the community in a positive and thoughtful way. Consider what’s best for the overall community. Do not make threats of violence, intimidate others, incite violence or intimidation against others, incite self-harm, stalk, follow, or otherwise harass others. Be mindful of your surroundings and of your fellow participants.
+
+Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+
+# Additional rules for online spaces
+
+For Deepgram’s official online spaces, like our YouTube & Twitch chats, we have some additional rules. Any of the following behaviors can result in a ban without warning.
+
+### DON'T SPAM
+
+Don't spam. We'll ban you.
+
+### KEEP IT LEGAL
+
+If it’s illegal, it’s not allowed on our websites or in our online spaces. Please don’t share links to pirated material or other nefarious things.
+
+### NO TROLLING
+
+Please be earnest. Don’t use excessive sarcasm to annoy or undermine other people. And don’t bait them with bad faith comments or abuse.
+
+### PORNOGRAPHY AND OTHER NSFW STUFF
+
+Please don’t post it or link to it. It doesn’t belong in our online spaces.
+
+### FOUL AND GRAPHIC LANGUAGE
+
+Please do not use excessive curse words. Additionally, do not use graphic sexual or violent language — again, think of our spaces as places for people of all ages.
+
+# Enforcement & Reporting
+
+If you are being harassed by a member of the Deepgram developer community, if you observe someone else being harassed, or you experience actions or behaviors that are contrary to our Code of Conduct, please report the behavior by contacting our team at [[email protected]](mailto:[email protected]).
+
+## 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:
+
+- Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct
+- https://eventhandler.community/conduct/, which itself is inspired by Quest, who in turn provides credit to Scripto, the #botALLY Code of Conduct, the LGBTQ in Tech code of Conduct, and the XOXO Code of Conduct.
+
+Community Impact Guidelines, which were copied from InnerSource Commons, were inspired by Mozilla’s code of conduct enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing Guidelines
+
+Want to contribute to this project? We ❤️ it!
+
+Here are a few types of contributions that we would be interested in hearing about.
+
+- Bug fixes
+  - If you find a bug, please first report it using Github Issues.
+  - Issues that have already been identified as a bug will be labeled `🐛 bug`.
+    - If you'd like to submit a fix for a bug, send a Pull Request from your own fork and mention the Issue number.
+      - Include a test that isolates the bug and verifies that it was fixed.
+- New Features
+  - If you'd like to accomplish something in the extension that it doesn't already do, describe the problem in a new Github Issue.
+    - Issues that have been identified as a feature request will be labeled `✨ enhancement`.
+    - If you'd like to implement the new feature, please wait for feedback from the project maintainers before spending
+      too much time writing the code. In some cases, `✨ enhancement`s may not align well with the project objectives at
+      the time.
+- Tests, Documentation, Miscellaneous
+  - If you think the test coverage could be improved, the documentation could be clearer, you've got an alternative
+    implementation of something that may have more advantages, or any other change we would still be glad hear about
+    it.
+    - If its a trivial change, go ahead and send a Pull Request with the changes you have in mind
+    - If not, open a Github Issue to discuss the idea first.
+- Snippets
+  - To add snippets:
+    - Add a directory in the `snippets` folder with the name of the language.
+    - Add one or more files in the language directory with snippets.
+    - Update the `package.json` to include the snippets you added.
+
+We also welcome anyone to work on any existing issues with the `👋🏽 good first issue` tag.
+
+## Requirements
+
+For a contribution to be accepted:
+
+- The test suite must be complete and pass
+- Code must follow existing styling conventions
+- Commit messages must be descriptive. Related issues should be mentioned by number.
+
+If the contribution doesn't meet these criteria, a maintainer will discuss it with you on the Issue. You can still
+continue to add more commits to the branch you have sent the Pull Request from.
+
+## How To
+
+1. Fork this repository on GitHub.
+1. Clone/fetch your fork to your local development machine.
+1. Create a new branch (e.g. `issue-12`, `feat.add_foo`, etc) and check it out.
+1. Make your changes and commit them. (Did the tests pass? No linting errors?)
+1. Push your new branch to your fork. (e.g. `git push myname issue-12`)
+1. Open a Pull Request from your new branch to the original fork's `main` branch.

KNOWN_ISSUES.md

@@ -0,0 +1,3 @@
+# Known Issues
+
+This is a list of known issues. For the latest list of all issues see the [Github Issues page](https://github.com/deepgram-startrs/nextjs-live-transcription/issues).