browsix 1.0.0__tar.gz

browsix-1.0.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+
+name: Bug Report
+about: Report a bug to help us improve browsix
+title: "[BUG] "
+labels: bug
+---
+
+## Description
+
+A clear and concise description of the bug.
+
+## Steps to Reproduce
+
+1. Run `browsix ...`
+2. ...
+3. See error
+
+## Expected Behavior
+
+What you expected to happen.
+
+## Actual Behavior
+
+What actually happened.
+
+## Environment
+
+- browsix version: `browsix --version` (or pip show browsix)
+- Python version: `python --version`
+- OS: [e.g. Windows 11, Ubuntu 22.04, macOS 14]
+- Browser: [e.g. Chrome 125, Edge 125, Brave 1.65]
+- Backend: [cdp / bidi]
+
+## Additional Context
+
+Any other context, logs, or screenshots.

browsix-1.0.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+
+name: Feature Request
+about: Suggest a new feature or improvement for browsix
+title: "[FEATURE] "
+labels: enhancement
+---
+
+## Problem
+
+A clear description of the problem this feature would solve.
+
+## Proposed Solution
+
+A description of what you want to happen.
+
+## Alternatives Considered
+
+Any alternative solutions or features you've considered.
+
+## Additional Context
+
+Any other context, examples, or references.

browsix-1.0.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+## Summary
+
+Brief description of the changes.
+
+## Type of Change
+
+- [ ] Bug fix (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
+- [ ] Refactor / cleanup
+
+## Checklist
+
+- [ ] Code follows PEP 8 and passes `ruff check .`
+- [ ] Type hints on all parameters and return types
+- [ ] `mypy browsix/` passes
+- [ ] Tests added or updated for changes
+- [ ] `pytest tests/unit/ -v` passes
+- [ ] Conventional commit message used
+- [ ] Documentation updated if needed

browsix-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,56 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  lint:
+    name: Lint (ruff)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install "ruff>=0.4"
+      - run: ruff check .
+
+  typecheck:
+    name: Typecheck (mypy)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install -e ".[dev,cdp,bidi]"
+      - run: mypy browsix/ --ignore-missing-imports
+
+  unit-tests:
+    name: Unit tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install -e ".[dev,cdp,bidi]"
+      - run: pytest tests/unit/ -m unit -v
+
+  integration-tests:
+    name: Integration tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - uses: browser-actions/setup-chrome@v1
+        with:
+          chrome-version: stable
+      - run: pip install -e ".[dev,cdp]"
+      - run: pytest tests/integration/ -m integration -v
+        continue-on-error: true

browsix-1.0.0/.github/workflows/docs.yml

@@ -0,0 +1,42 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  build-docs:
+    name: Build mkdocs site
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install -e ".[docs]"
+      - run: mkdocs build --strict
+      - uses: actions/configure-pages@v5
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site/
+
+  deploy-docs:
+    name: Deploy to GitHub Pages
+    needs: build-docs
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

browsix-1.0.0/.github/workflows/release.yml

@@ -0,0 +1,62 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+jobs:
+  build:
+    name: Build sdist + wheel
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install "build>=1.2"
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish-pypi:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  publish-docs:
+    name: Publish docs to GitHub Pages
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install -e ".[docs]"
+      - run: mkdocs build --strict
+      - uses: actions/configure-pages@v5
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site/
+      - id: deployment
+        uses: actions/deploy-pages@v4

browsix-1.0.0/.github/workflows/serve-test.yml

@@ -0,0 +1,22 @@
+name: Serve Mode Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  serve-test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install -e ".[cdp,serve,dev]" pytest-aiohttp
+      - uses: browser-actions/setup-chrome@v1
+      - name: Run serve mode unit tests
+        run: pytest tests/unit/test_serve.py -v
+      - name: Run serve mode integration tests
+        run: pytest tests/integration/test_serve.py -v -m integration

browsix-1.0.0/.gitignore

@@ -0,0 +1,25 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+dist/
+build/
+.eggs/
+*.egg
+.venv/
+venv/
+env/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.coverage
+coverage.xml
+htmlcov/
+*.so
+.idea/
+.vscode/
+*.swp
+*.swo
+site/
+spike.png
+spike.py

browsix-1.0.0/CHANGELOG.md

@@ -0,0 +1,80 @@
+# Changelog
+
+All notable changes to browsix are documented in this file.
+
+## v1.0.0 — 2026-07-05
+
+### Added
+
+- Error handling with consistent exit codes (0 success, 1 browser, 2 config, 3 backend)
+- `Output.error()`, `Output.success()`, `Output.info()` with optional rich formatting
+- Global CLI flags: `--verbose`, `--quiet`, `--version`
+- Shell completions command (`browsix completions <shell>`)
+- GitHub Actions CI workflow (lint, typecheck, unit tests, integration tests)
+- GitHub Actions release workflow (PyPI publish, GitHub Pages docs)
+- mkdocs documentation site with material theme
+- Comprehensive README with badges, examples, and comparison table
+- Troubleshooting guide
+- Contributing guide
+
+### Changed
+
+- Version bumped to 1.0.0
+- Development status classifier updated to "Production/Stable"
+- CLI help strings improved for all commands and options
+- All error messages now use `Output.error()` for consistent formatting
+
+## v0.3.0 — 2026-06-28
+
+### Added
+
+- Emulation commands: device, viewport, geolocation, timezone, dark mode
+- `EmulationAction` class for emulation operations
+- `MultiAction` class for YAML multi-action execution
+- `multi` CLI command with YAML config parsing
+- `backends` CLI command to list available backends
+- `install_check` CLI command to check backend installation status
+- Global `--backend` CLI flag for backend selection
+- `WAIT_PRESETS` and `THROTTLE_PRESETS` config dictionaries
+- `EmulationParams` dataclass
+- `MultiConfigError` exception for invalid multi configs
+- `BackendManager.install_check()` method
+- `BackendManager.list_available()` method
+- `BackendManager.select(preferred)` with preferred backend support
+
+## v0.2.0 — 2026-06-14
+
+### Added
+
+- DOM operations: get, query, set attribute, remove attribute, remove, focus, scroll
+- HAR capture for network traffic analysis
+- Cookie management: get, set, delete, clear
+- Extra HTTP headers setting
+- User-Agent override
+- Browser context management
+- Tab management: list, new, close, activate
+- Console message capture
+- Browser log capture
+- Scrape command for batch URL processing
+- `DOMAction`, `HARAction`, `TabsAction`, `ConsoleAction` classes
+- `CookieParams`, `HarParams`, `DOMParams`, `TabsParams`, `ConsoleParams` dataclasses
+- Device presets dictionary
+- Paper sizes dictionary
+
+## v0.1.0 — 2026-05-30
+
+### Added
+
+- Initial browsix release
+- `AbstractBackend` interface with all core methods
+- `CDPBackend` implementation using cdpwave
+- `BiDiBackend` minimal implementation using bidiwave
+- `BackendManager` for backend registration and selection
+- Core CLI commands: screenshot, pdf, eval, navigate, back, forward, reload, stop
+- `ScreenshotAction`, `PDFAction`, `EvalAction`, `NavigateAction` classes
+- `BrowserOptions`, `ScreenshotParams`, `PDFParams`, `EvalParams` dataclasses
+- `WaitStrategy` with load, domcontentloaded, selector, networkidle strategies
+- `Output` helpers for bytes, JSON, text, CSV
+- Exception hierarchy: `BrowsixError`, `BackendNotAvailableError`, `NavigationError`, `WaitTimeoutError`, `ElementNotFoundError`
+- Typer CLI with help strings and no-args-is-help
+- Unit and integration test infrastructure

browsix-1.0.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# 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 for the overall community, not just us as
+  individuals
+
+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 with 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
+**mathias.paulenko@outlook.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][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://www.mozilla.org/en-US/about/governance/policies/anti-harassment/
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

browsix-1.0.0/CONTRIBUTING.md

@@ -0,0 +1,124 @@
+# Contributing to browsix
+
+Thank you for your interest in contributing to browsix! This document outlines
+the process for contributing bug reports, feature requests, code changes, and
+documentation improvements.
+
+## Getting Started
+
+### Prerequisites
+
+- Python 3.11 or higher
+- A Chromium-based browser (Chrome, Edge, Brave, or Chromium)
+- Git
+
+### Development Setup
+
+```bash
+git clone https://github.com/MathiasPaulenko/browsix.git
+cd browsix
+pip install -e ".[cdp,dev]"
+```
+
+### Running Tests
+
+```bash
+# Unit tests (no browser required)
+pytest tests/unit/ -v --cov=browsix --cov-report=term-missing
+
+# Linting and type checking
+ruff check .
+mypy browsix/
+
+# Spike test (requires Chrome installed)
+python spike.py
+```
+
+### Project Structure
+
+```
+browsix/
+├── browsix/              # Source code
+│   ├── cli/              # Typer CLI commands
+│   ├── backend/          # Backend abstraction (CDPBackend, BiDiBackend)
+│   ├── actions/          # Action classes (ScreenshotAction, etc.)
+│   ├── config.py         # Dataclasses for params and presets
+│   ├── auth.py           # Auth context loader
+│   ├── output.py         # Output helpers (file, stdout, JSON)
+│   └── exceptions.py     # Custom exceptions
+├── tests/                # Test suite
+│   ├── unit/             # Unit tests with mocks
+│   └── integration/      # Integration tests (require Chrome)
+├── docs/                 # Documentation
+└── pyproject.toml        # Project configuration
+```
+
+## How to Contribute
+
+### Reporting Bugs
+
+Before creating a bug report, check existing issues to avoid duplicates. When
+creating a bug report, use the **Bug Report** issue template and include:
+
+1. A clear description of the problem
+2. Steps to reproduce the issue
+3. Expected vs actual behavior
+4. browsix version, Python version, OS, and browser version
+5. Minimal command example (if applicable)
+
+### Suggesting Features
+
+Use the **Feature Request** issue template. Describe:
+
+1. The problem your feature would solve
+2. The proposed solution
+3. Alternatives you've considered
+
+### Pull Requests
+
+1. **Fork** the repository and create your branch from `main`
+2. **Write tests** for your changes — unit tests are required for new features
+3. **Ensure all checks pass**:
+   ```bash
+   ruff check .
+   mypy browsix/
+   pytest tests/unit/ -v
+   ```
+4. **Use conventional commit messages**:
+   - `feat:` new feature
+   - `fix:` bug fix
+   - `docs:` documentation only
+   - `refactor:` code change that neither fixes a bug nor adds a feature
+   - `test:` adding or correcting tests
+   - `chore:` tooling, dependencies, config
+5. **Keep PRs focused** — one feature or fix per PR
+6. **Update documentation** if your change affects the public API
+
+### Code Style
+
+- Follow PEP 8 (enforced by ruff, line-length=100)
+- Use type hints for all function parameters and return types
+- Write docstrings in Google style for all public methods
+- Prefer small, single-responsibility functions
+- No comments that don't add value — the code should be self-documenting
+
+## Release Process
+
+Releases are managed by the maintainer:
+
+1. Version bump in `pyproject.toml` and `browsix/__init__.py`
+2. Create annotated git tag (`vX.Y.Z`)
+3. GitHub Actions builds and publishes to PyPI automatically
+
+Versioning follows [Semantic Versioning](https://semver.org/):
+- **MAJOR**: breaking API changes
+- **MINOR**: new features, backwards compatible
+- **PATCH**: bug fixes, backwards compatible
+
+## Questions?
+
+Feel free to open a **Question** issue or reach out at
+**mathias.paulenko@outlook.com**.
+
+By participating in this project, you agree to abide by the
+[Code of Conduct](CODE_OF_CONDUCT.md).

browsix-1.0.0/Dockerfile

@@ -0,0 +1,12 @@
+FROM python:3.12-slim
+
+RUN apt-get update && apt-get install -y \
+    chromium \
+    --no-install-recommends \
+    && rm -rf /var/lib/apt/lists/*
+
+RUN pip install browsix[cdp,serve]
+
+EXPOSE 8080
+
+CMD ["browsix", "serve", "--port", "8080", "--host", "0.0.0.0"]

browsix-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Mathias Paulenko
+
+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.