Skip CLI detector for URLs (avoids Puppeteer install)

URLs should use browser visualization + LLM analysis instead of
the CLI detector, which would need to install Puppeteer and its
dependencies first.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Paul Bakaus
2026-03-19 13:12:31 -07:00
co-authored by Claude Opus 4.6
parent 4591e51b6f
commit a24328a0fa
2 changed files with 4 additions and 2 deletions
+2 -1
View File
@@ -22,7 +22,8 @@ Before the manual critique, run the bundled deterministic detector. It catches 2
node scripts/detect-antipatterns.mjs --json [--fast] [target]
```
- Pass files, directories, or URLs as `[target]`
- Pass files or directories as `[target]`
- For URLs, skip the CLI scan (it requires Puppeteer installation). Instead, rely on browser visualization (below) and LLM analysis.
- For large directories (200+ scannable files), use `--fast` (regex-only, skips jsdom)
- For 500+ files, narrow scope to the most relevant subdirectory or ask the user
- Exit code 0 = clean, 2 = findings
+2 -1
View File
@@ -22,7 +22,8 @@ Before the manual critique, run the bundled deterministic detector. It catches 2
node scripts/detect-antipatterns.mjs --json [--fast] [target]
```
- Pass files, directories, or URLs as `[target]`
- Pass files or directories as `[target]`
- For URLs, skip the CLI scan (it requires Puppeteer installation). Instead, rely on browser visualization (below) and LLM analysis.
- For large directories (200+ scannable files), use `--fast` (regex-only, skips jsdom)
- For 500+ files, narrow scope to the most relevant subdirectory or ask the user
- Exit code 0 = clean, 2 = findings