export declare const traceUtilsDoc = "\n<trace-utils-cli>\n# Trace Utils\n\nCLI and library for inspecting Playwright `trace.zip` files.\n\n## Usage\n\nVia sandbox-cli:\n```bash\nsandbox-cli trace-utils <command> [options]\n```\n\n---\n\n## `steps`\n\nList all test steps from a trace.\n\n```bash\nsandbox-cli trace-utils steps --file <path> [--json]\n```\n\n| Option | Description | Default |\n|--------|-------------|---------|\n| `--file` | Path or URL to trace.zip | *required* |\n| `--json` | Output as JSON | `false` |\n\n---\n\n## `screenshots`\n\nExtract screenshots from a trace. Use either `--step` or `--start`/`--end` (one is required).\n\n```bash\n# By step ID\nsandbox-cli trace-utils screenshots --file <path> --step <id> [options]\n\n# By time range\nsandbox-cli trace-utils screenshots --file <path> --start <time> --end <time> [options]\n```\n\n| Option | Description | Default |\n|--------|-------------|---------|\n| `--file` | Path or URL to trace.zip | *required* |\n| `--step` | Step callId to extract around | - |\n| `--start` | Start time (HH:MM:SS.mmm) | - |\n| `--end` | End time (HH:MM:SS.mmm) | - |\n| `--page` | Page ID to filter by (required for multi-page traces with time-based extraction) | - |\n| `--before` | Milliseconds before step (only with --step) | `2000` |\n| `--after` | Milliseconds after step (only with --step) | `2000` |\n| `--max` | Maximum screenshots | `10` |\n| `--output` | Output directory | auto-generated in `/tmp` |\n\n**Examples:**\n\n```bash\n# 1. List steps to find callId or timestamps\nsandbox-cli trace-utils steps --file ./trace.zip\n\n# Output:\n# [test.step@36] locator.click(getByRole('button', { name: 'Create' })) (page@abc123)\n#   00:02:06.434 \u2192 00:02:06.543 (110ms)\n\n# 2a. Extract by step ID\nsandbox-cli trace-utils screenshots --file ./trace.zip --step \"test.step@36\"\n\n# 2b. Extract by time range (for multi-page traces, --page is required)\nsandbox-cli trace-utils screenshots --file ./trace.zip --start 00:02:06.000 --end 00:02:07.000 --page \"page@abc123\"\n```\n\n---\n\n## `network`\n\nSearch network requests. For multi-page traces, either `--step` or `--page` is required.\n\n```bash\nsandbox-cli trace-utils network --file <path> [filters] [options]\n```\n\n| Option | Description | Default |\n|--------|-------------|---------|\n| `--file` | Path or URL to trace.zip | *required* |\n| `--step <callId>` | Filter to requests during a specific step | - |\n| `--page` | Page ID to filter by (required for multi-page traces without --step) | - |\n| `--before <ms>` | Time before step to include (with --step) | `2000` |\n| `--after <ms>` | Time after step to include (with --step) | `2000` |\n| `--errors` | Show only failed requests (4xx, 5xx, no response) | - |\n| `--url <pattern>` | Filter by URL pattern (regex) | - |\n| `--method <method>` | Filter by HTTP method | - |\n| `--status <codes>` | Filter by status codes (e.g., `404,500`) | - |\n| `--json` | Output as JSON | `false` |\n\n**Examples:**\n\n```bash\n# Show all failed requests (for multi-page traces, specify --page)\nsandbox-cli trace-utils network --file ./trace.zip --errors --page \"page@abc123\"\n\n# Search for specific API calls\nsandbox-cli trace-utils network --file ./trace.zip --url \"/api/v1/users\" --page \"page@abc123\"\n\n# Failed POST requests\nsandbox-cli trace-utils network --file ./trace.zip --errors --method POST --page \"page@abc123\"\n\n# Network requests during a specific step (--page not required)\nsandbox-cli trace-utils network --file ./trace.zip --step \"pw:api@32\"\n```\n\n---\n\n## `console`\n\nView browser console output. For multi-page traces, `--page` is required.\n\n```bash\nsandbox-cli trace-utils console --file <path> [options]\n```\n\n| Option | Description | Default |\n|--------|-------------|---------|\n| `--file` | Path or URL to trace.zip | *required* |\n| `--page` | Page ID to filter by (required for multi-page traces) | - |\n| `--level` | Minimum level: `error`, `warning`, `info`, `debug` | `error` |\n| `--json` | Output as JSON | `false` |\n| `--search` | Filter logs containing text | - |\n\n---\n\n## `dom-snapshot`\n\nExtract DOM snapshot from a trace. Use either `--step` or `--time` (one is required).\n\n```bash\n# By step ID\nsandbox-cli trace-utils dom-snapshot --file <path> --step <id> [options]\n\n# By time (for multi-page traces, --page is required)\nsandbox-cli trace-utils dom-snapshot --file <path> --time <time> --page <pageId> [options]\n```\n\n| Option | Description | Default |\n|--------|-------------|---------|\n| `--file` | Path or URL to trace.zip | *required* |\n| `--step` | Step callId to extract snapshot for | - |\n| `--time` | Time to extract snapshot at (HH:MM:SS.mmm) | - |\n| `--page` | Page ID to filter by (required for multi-page traces with --time) | - |\n| `--type` | Snapshot type: `before`, `after`, `input` (only with --step) | `before` |\n| `--output` | Output file path | - |\n| `--json` | Output as JSON | `false` |\n\n**Snapshot types:**\n\n- `before` - DOM state when the step starts (default)\n- `after` - DOM state when the step completes\n- `input` - DOM state at the moment of user input (for click/fill actions)\n\n> **Tip for assertions:** For `expect` steps like `toBeVisible`, use `--type after` to see the DOM state when the assertion passed. The `before` snapshot may show a loading state if the test was waiting for an element to appear.\n\n**Examples:**\n\n```bash\n# 1. List steps to find callId\nsandbox-cli trace-utils steps --file ./trace.zip\n\n# 2. Extract DOM snapshot before a click step\nsandbox-cli trace-utils dom-snapshot --file ./trace.zip --step \"pw:api@32\" --type before\n\n# 3. Extract DOM snapshot after a step and save to file\nsandbox-cli trace-utils dom-snapshot --file ./trace.zip --step \"pw:api@32\" --type after --output ./snapshot.html\n\n# 4. For assertions, use --type after to see the DOM when assertion passed\nsandbox-cli trace-utils dom-snapshot --file ./trace.zip --step \"expect@43\" --type after\n\n# 5. Extract DOM snapshot at a specific time\nsandbox-cli trace-utils dom-snapshot --file ./trace.zip --time 00:02:06.434\n\n# 6. Get snapshot as JSON\nsandbox-cli trace-utils dom-snapshot --file ./trace.zip --step \"pw:api@32\" --json\n```\n\n**Output (default):**\n```\n# DOM Snapshot: locator.click\n# Step: pw:api@32\n# URL: https://example.com/dashboard\n# Viewport: 1280x720\n# Snapshot type: before\n\n<!DOCTYPE html>\n<html>\n  <head>\n    <title>Dashboard</title>\n    ...\n  </head>\n  <body>\n    ...\n  </body>\n</html>\n```\n\n</trace-utils-cli>\n";
//# sourceMappingURL=trace-utils-docs.d.ts.map