Initial

Author: msilivonik-sc

.editorconfig

@@ -0,0 +1,28 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+trim_trailing_whitespace = true
+
+# Code files
+[*.{js,jsx,ts,tsx,json,css,scss,html}]
+indent_style = space
+indent_size = 2
+max_line_length = 120
+
+# Markdown files
+[*.md]
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = false
+
+# Package files
+[{package.json,package-lock.json}]
+indent_style = space
+indent_size = 2

.gitignore

@@ -0,0 +1,42 @@
+# Dependencies
+node_modules/
+
+# Build output
+dist/
+build/
+*.tsbuildinfo
+
+# Auto-generated at build time by scripts/sync-version.sh
+src/version.ts
+
+# Environment
+.env
+.env.local
+.env.*.local
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# Testing
+coverage/
+.nyc_output/
+
+# Misc
+*.tmp
+*.temp
+

.husky/pre-commit

@@ -0,0 +1 @@
+npx lint-staged

.npmignore

@@ -0,0 +1,31 @@
+# Source files
+src/
+*.ts
+!*.d.ts
+
+# Config files
+tsconfig.json
+tsconfig.cjs.json
+.eslintrc*
+.prettierrc*
+
+# Development files
+.git/
+.github/
+.vscode/
+.idea/
+
+# Tests
+*.test.*
+*.spec.*
+__tests__/
+__mocks__/
+
+# Documentation
+*.md
+!README.md
+
+# Misc
+.DS_Store
+*.log
+

.npmrc

@@ -0,0 +1,2 @@
+registry=https://registry.npmjs.org/
+@snap:registry=https://registry.npmjs.org/

.nvmrc

@@ -0,0 +1 @@
+v24.14.0

.prettierignore

@@ -0,0 +1,13 @@
+# Dependencies
+node_modules/
+
+# Build outputs
+dist/
+build/
+
+# Package files
+package-lock.json
+
+# Logs
+*.log
+

.prettierrc

@@ -0,0 +1,3 @@
+{
+  "printWidth": 120
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+**Code of Conduct**
+
+**Our Pledge**
+
+We as members, contributors, and leaders of the Camera Kit Web React Bindings community 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
+
+**Our Enforcement Responsibilities**
+
+Camera Kit Web React Bindings 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.
+
+Camera Kit Web React Bindings 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 email 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 opensource@snap.com. 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](https://www.contributor-covenant.org/), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).

CONTRIBUTING.md

@@ -0,0 +1,66 @@
+**Contributing guide**
+
+We welcome community contributions and appreciate your time and effort in helping improve this project. Before getting started, please take a moment to review these guidelines.
+
+1. **Code of Conduct**
+
+We want this project to be a welcoming space for everyone. By contributing, you agree to follow our Code of Conduct and help keep the community respectful and inclusive.
+
+2. **How to Contribute**
+
+We welcome contributions in various forms, including:
+
+- Bug fixes
+- New features
+- Documentation improvements
+- Tests and performance optimizations
+
+To contribute, follow these steps:
+
+1. **Fork the repository** and create your branch from `main`.
+2. **Make your changes**, ensuring they align with our coding standards (§4 below).
+3. **Run `npm test`** to ensure your changes do not break existing functionality.
+4. **Run `npm run format`** to ensure coding guidelines are followed.
+5. **Submit a pull request (PR)** with a clear description of the changes.
+6. A maintainer will review your PR, suggest any necessary changes, and merge it once approved.
+
+**Commit Messages**
+
+Use clear and descriptive commit messages. Follow the conventional commit format when possible:
+
+feat: Add new authentication method  
+fix: Resolve issue with session timeout  
+docs: Update README with new installation steps
+
+3. **Contributor License Agreement**
+
+We do not require a signed Contributor License Agreement (CLA) to be on file. However, by contributing, you agree to license your submission as follows:
+
+By submitting a contribution, you:
+
+- Represent and warrant that it is your original work, or you have sufficient rights to submit it under these terms and conditions.
+- Grant the project maintainers and users the right to use, modify, and distribute it under the MIT license (see LICENSE file); and
+- To the extent your contribution is covered by patents, grant a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license to the project maintainers and users to make, use, sell, offer for sale, import, and otherwise transfer your contribution as part of the project.
+- Shall ensure that any third-party code in your contribution is MIT-compatible and properly attributed.
+- Where permitted by law, waive any moral rights in your contribution (e.g., the right to object to modifications). If such rights cannot be waived, you agree not to assert them in a way that interferes with the project’s use of your contribution.
+
+4. **Coding Standards**
+
+To maintain a consistent codebase, please follow these guidelines:
+
+- Use the existing coding style and conventions.
+- Ensure all code changes are well-documented.
+- Write tests for new features and bug fixes.
+- Avoid introducing unnecessary dependencies.
+
+5. **Reporting Issues**
+
+If you find a bug or have a feature request, please open an [issue](../../issues) and provide as much detail as possible:
+
+- Steps to reproduce (if applicable)
+- Expected and actual behavior
+- Suggested solutions (if any)
+
+6. **Recognition**
+
+We use the [All Contributors](https://allcontributors.org/) specification to recognize community members. If your contribution is merged, you will be added to the project's list of contributors. This includes contributions of all kinds—code, documentation, design, testing, and more.