@qubiqlabs/webqa

npm launcher for the WebQA CLI. The tarball bundles the Python package under python/, so npx webqa does not need PyPI for the webqa package itself (dependencies still come from PyPI).

Install

npm install -g @qubiqlabs/webqa
# or one-shot:
npx @qubiqlabs/webqa init

Requires Python 3.11+ on PATH (including 3.14). Prefer 64-bit builds with wheels. WebQA vendors tiktoken encodings and uses certifi for SSL so codegen can start offline / on locked-down Windows without needing a second Python install.

The npm package ships how-to docs under docs/ (same idea as WebPilot). webqa init copies them into the project. The launcher always runs python -m webqa — no webqa.exe is required.

On first run the launcher creates ~/.webqa/venv and installs the core CLI (enough for webqa init). It then tries AI extras (WebQA-Browser / WebQA-Codegen); if that fails (often Rust/MSVC on Windows), init still works. Install extras later:

# use the managed venv's python:
python -c "from webqa.deps import install_ai_deps; install_ai_deps()"

If install fails with metadata-generation-failed, use Python 3.12, delete %USERPROFILE%\.webqa, and retry (npm install -g @qubiqlabs/webqa@latest then webqa init).

Also picks up a project .venv / venv if present.

Overrides:

• WEBQA_BIN — path to the Python webqa executable
• WEBQA_PYTHON — Python interpreter to prefer

Usage

webqa init --clone https://github.com/org/app.git --dest ./app
webqa run cases/example.txt

LLM API keys come from environment variables (see upstream README).