Basic Usage
The scan command
Section titled “The scan command”frontend-qa scan [options]scan is the default command — frontend-qa with no subcommand runs it.
Targeting
Section titled “Targeting”If you omit --url, frontend-qa first checks for an already-running dev
server; if none is found, it detects a Vite or Next.js project in the
current directory, picks the right package manager, and launches a dev
server itself for the duration of the scan.
frontend-qa scan --url http://localhost:3000Scanning multiple routes
Section titled “Scanning multiple routes”frontend-qa scan --route / --route /about --route /pricingDefaults to ['/'] if omitted. Pass --discover-routes to have
frontend-qa crawl same-origin links from the routes you gave it and scan
those too.
frontend-qa scan --discover-routesViewport
Section titled “Viewport”frontend-qa scan --viewport 1280x800Headed mode
Section titled “Headed mode”Runs with a visible browser window instead of headless — useful when debugging a scan interactively:
frontend-qa scan --headedTimeout
Section titled “Timeout”Per-route navigation timeout in milliseconds (default 30000):
frontend-qa scan --timeout 60000Output directory
Section titled “Output directory”frontend-qa scan --out ./qa-outputDefaults to .local/frontend-qa/runs/<runId>/ under the project root.
Capturing a HAR file
Section titled “Capturing a HAR file”frontend-qa scan --harFailing the process on issues
Section titled “Failing the process on issues”frontend-qa scan --fail-on critical # only exit non-zero on criticalfrontend-qa scan --fail-on never # always exit 0Default is high. See Configuration Reference
for the full option table and every default.
Opt-in engines
Section titled “Opt-in engines”frontend-qa scan --a11y --perf --visualCovered in depth in their own guides — these are slower checks so they’re off unless requested. Runtime collectors (console, network, screenshot, timing) always run.