buninu-browser 0.0.2

package/vendor/happy-dom/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# 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, 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
+david@ortner.se.
+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,
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://github.com/capricorn86/happy-dom
+
+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.

package/vendor/happy-dom/CONTRIBUTING.md

@@ -0,0 +1,147 @@
+# Setup
+
+## Install
+
+### 1. Install Bun
+
+To be able to run all tests in the "./packages/global-registrator" package, you need to install [Bun](https://bun.sh/).
+
+<details>
+  <summary>Linux & MacOS</summary>
+
+```bash
+curl -fsSL https://bun.sh/install | bash
+```
+
+</details>
+<details>
+  <summary>Windows</summary>
+
+```bash
+powershell -c "irm bun.sh/install.ps1 | iex"
+```
+
+</details>
+
+### 2. Install dependencies
+
+```bash
+npm install
+```
+
+## Compile
+
+```bash
+npm run compile
+```
+
+## Watch
+
+```bash
+npm run watch
+```
+
+## Test
+
+**Run tests**
+
+```bash
+npm test
+```
+
+**Watch tests**
+
+```bash
+npm run test:watch
+```
+
+## Debug
+
+1. Go to the package you wish to test and debug in the terminal (e.g. `cd ./packages/happy-dom`)
+2. Write "debugger;" at the place you want to place a breakpoint in the code
+3. Run `npm run test:debug` in the terminal
+4. Open Chrome
+5. Open developer tools
+6. A green ball should appear to the left of the menu bar in developer tools
+7. Click on the green ball
+8. Click continue to jump to your breakpoint
+
+# Pull Request Guidelines
+
+Checkout a topic branch from a base branch, e.g. "master", and merge back against that branch.
+
+## Title
+
+The title of the pull request should be in the format of "type: [#issue] description". The type can be one of the following:
+
+- feat: A new feature
+- fix: A bug fix
+- chore: A change that does not fix a bug or add a feature
+- BREAKING CHANGE: A change that breaks backward compatibility
+
+The issue is optional and can be omitted if the pull request does not relate to an issue.
+
+## Commit Convention
+
+There is no strict commit convention, but it's recommended to follow the same format as the pull request title for commit messages. This will make it easier to understand the purpose of each commit and will help with generating changelogs.
+
+It's OK to have multiple commits in a pull request. The commits will be squashed into one commit when the pull request is merged.
+
+## Review
+
+All pull requests must be approved by @capricorn86 who is the founder and main maintainer of the project. Other maintainers and contributors can also approve pull requests, but their approval is not required for the pull request to be merged. Hopefully in the future we will have more maintainers who can approve pull requests.
+
+The review process may take some time, so please be patient. If you have any questions or need help with your pull request, please ask for help in the pull request or in the issue.
+
+# Tests
+
+Make sure to add tests for your changes. Run your test in a real browser to make sure that the test tests what a real browser would do (e.g. by running the code in the browser console).
+
+Pull requests will not be merged if they do not have tests that cover the changes. If you are not sure how to write tests for your changes, please ask for help in the pull request or in the issue and a maintainer will help you.
+
+## If it's a feature
+
+Add tests that cover the new feature and all edge cases you can think of. You only need to test the public API. Internal functionality should be tested through the public API.
+
+One way to do this is to read the the added code line by line and whenever you see a new function or a new code path, ask yourself "how can I test this?" and then write a test for it.
+
+## If it's a bug fix
+
+Add a test that reproduces the bug and then fix the bug. The test should fail before the bug is fixed and should pass after the bug is fixed.
+
+# AI Contributions
+
+We welcome AI as a personal assistant when contributing. However, we strongly believe that a real person must be behind every issue and pull request. The code itself is not the most important part. If it where, everything for Happy DOM would have been automated already.
+
+You are responsible for the content of your contribution, even if it was generated by AI. Make sure to review and test the generated code to ensure it meets the project's standards.
+
+All issues and pull requests must be opened by a real person using the official templates. If AI assisted in creating a pull request, please disclose the tool used (e.g. Claude, Codex, Copilot).
+
+Pull requests or issues generated by AI with no or limited human involvement (e.g. by an automated agent) will be labeled "Maybe automated" by the maintainers. An additional label with either "Will be closed" or "Needs work" may be added to indicate actions needed. If the PR gets the label "Will be closed", it's expected to get a human response within 3 days, otherwise the PR will be closed. The response is expected to be genuine, meaning it should not be written by an LLM. The maintainers reserve the right to decide, based on their experience, whether a response was AI-generated.
+
+These measures help reduce maintenance burden and keep work efficient.
+
+# Coding Guidelines
+
+Happy DOM is written in TypeScript using an object-oriented programming style. We use classes and inheritance to structure the code. We also use interfaces to define the public API of the classes in some cases. Utility functions are also defined in classes, usually as static methods. The DOM functionality contains a lot of complex functionality, so we organize it into classes to make it easier to understand and maintain (e.g. `File.getName()` gives context compared to `getName()`).
+
+The code is documented with JSDoc comments. The comments should be clear and concise, and should explain the purpose of the code and how to use it. The comments should also include examples if necessary. The JSDoc comments are part of the public API and should be written in a way that is easy to understand for users of the library.
+
+When making a contribution, try to follow the existing coding style and conventions as much as possible. This will make it easier for the maintainers to review your code and will increase the chances of your pull request being merged.
+
+# Dependencies
+
+Happy DOM aims at being lightweight and fast, so we try to minimize the number of dependencies. We only use dependencies that are necessary for the functionality of the library. If you want to add a dependency, please make sure to justify why it is necessary and how it will benefit the library.
+
+Each dependency adds maintenance burden and can potentially introduce security vulnerabilities, so we are careful with adding dependencies.
+
+It's many times better to write a few lines of code yourself than to add a dependency for something that can be easily implemented. If you are not sure whether a dependency is necessary, please ask for help in the pull request or in the issue.
+
+# Release Process
+
+Releases are triggered manually by the maintainers. The release process is as follows:
+
+1. Merge all pull requests that are ready to be released into the main branch.
+2. Trigger the release workflow, which will generate a new version based on the commit messages and publish it to NPM.
+3. A GitHub release will be created with the changelog and the new version.
+4. The new version will be available on NPM.

package/vendor/happy-dom/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 David Ortner (capricorn86)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/vendor/happy-dom/README.md

@@ -0,0 +1,62 @@
+<h1 align="center">
+    <img alt="Happy DOM Logo" src="https://github.com/capricorn86/happy-dom/raw/master/docs/happy-dom-logo.jpg" />
+</h1>
+<p align="center">
+    A JavaScript implementation of a web browser without its graphical user interface.
+</p>
+
+<p align="center">
+    <a href="https://www.npmjs.com/package/happy-dom">
+        <img alt="Published on NPM" src="https://img.shields.io/npm/v/happy-dom.svg">
+    </a>
+</p>
+
+<p align="center">
+    <a href="https://github.com/capricorn86/happy-dom/wiki/">Documentation</a> | <a href="https://github.com/capricorn86/happy-dom/wiki/Getting-started">Getting started</a> | <a href="https://github.com/capricorn86/happy-dom/wiki/Setup-as-Test-Environment">Setup as Test Environment</a>
+</p>
+
+## DOM Features
+
+- Custom Elements (Web Components)
+
+- Declarative Shadow DOM
+
+- Mutation Observer
+
+- Tree Walker
+
+- Fetch API
+
+And much more..
+
+## Works With
+
+- [Vitest](https://vitest.dev/)
+- [Bun](https://bun.sh)
+- [Jest](https://jestjs.io/)
+- [Testing Library](https://testing-library.com/)
+- [Google LitElement](https://lit.dev/)
+- [Vue](https://vuejs.org/)
+- [React](https://reactjs.org)
+- [Svelte](https://svelte.dev/)
+- [Angular](https://angular.dev/)
+
+## Sponsors
+
+<p align="center"><b>Sponsors</b></p>
+
+<p align="center">
+    <a href="https://sentry.io/"><img alt="Sentry" width="50px" src="https://avatars.githubusercontent.com/u/1396951?s=200&v=4"></a>
+    &nbsp;&nbsp;
+    <a href="https://canonical.com/"><img alt="Canonical" width="50px" src="https://avatars.githubusercontent.com/u/53057619?s=200&v=4"></a>
+    &nbsp;&nbsp;
+    <a href="https://frontendmasters.com/"><img alt="Canonical" width="50px" src="https://avatars.githubusercontent.com/u/5613852?s=200&v=4"></a>
+</p>
+
+## Contributing
+
+See [Contributing Guide](https://github.com/capricorn86/happy-dom/blob/master/CONTRIBUTING.md).
+
+## License
+
+MIT License © 2019-Present [David Ortner](https://github.com/capricorn86)

package/vendor/happy-dom/SECURITY.md

@@ -0,0 +1,12 @@
+# Security Policy
+
+## Supported Versions
+
+| Version   | Supported          |
+| --------- | ------------------ |
+| > 15.10.0 | :white_check_mark: |
+| < 15.10.0 | :x:                |
+
+## Reporting a Vulnerability
+
+Use the [Github Vulnaribilty Reporter](https://github.com/capricorn86/happy-dom/security) tool to report your findings.

package/vendor/happy-dom/cspell.json

@@ -0,0 +1,34 @@
+{
+    "version": "0.2",
+    "ignorePaths": [],
+    "dictionaryDefinitions": [],
+    "dictionaries": [],
+    "words": [
+        "altgraph",
+        "antiquewhite",
+        "clonable",
+        "Contoso",
+        "darkmagenta",
+        "ICSS",
+        "IECMA",
+        "Immediates",
+        "ISVG",
+        "oncompositionend",
+        "oncompositionstart",
+        "oncompositionupdate",
+        "oncontentvisibilityautostatechange",
+        "onpointerrawupdate",
+        "onscrollsnapchange",
+        "onscrollsnapchanging",
+        "onsearch",
+        "referrerpolicy",
+        "Registrator",
+        "steppable",
+        "unnestable",
+        "vmax",
+        "vmin",
+        "xlink"
+    ],
+    "ignoreWords": [],
+    "import": []
+}

package/vendor/happy-dom/integration-test/.editorconfig

@@ -0,0 +1,8 @@
+# EditorConfig is awesome: http://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Indentation override for all JS under lib directory
+[{**.js,**.ts,**.json}]
+indent_style = tab

package/vendor/happy-dom/integration-test/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 David Ortner (capricorn86)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/vendor/happy-dom/integration-test/README.md

@@ -0,0 +1 @@
+This package is used internally for testing the integration of Happy DOM in various environments.

package/vendor/happy-dom/integration-test/package.json

@@ -0,0 +1,24 @@
+{
+	"name": "@happy-dom/integration-test",
+	"private": true,
+	"version": "0.0.0",
+	"license": "MIT",
+	"author": "David Ortner",
+	"description": "Private package used for integration testing of Happy DOM.",
+	"type": "module",
+	"publishConfig": {
+		"access": "restricted"
+	},
+	"scripts": {
+		"test": "cd ./test && ls | node --disallow-code-generation-from-strings --test && node --disallow-code-generation-from-strings ./browser-exception-observer/BrowserExceptionObserver.test.js",
+		"test:debug": "cd ./test && ls | node --inspect-brk"
+	},
+	"devDependencies": {
+		"happy-dom": "^0.0.0",
+		"@types/node": ">=20.0.0",
+		"express": "^4.20.0"
+	},
+	"engines": {
+		"node": ">=20.0.0"
+	}
+}