Skip to content

npx liarjs: how is "your local Chrome" located, and can i pin the binary? #86

Description

@matthewm755

quickstart:

npx liarjs                                 # your local Chrome
npx liarjs --headless --min-score 60       # CI gate

--cdp is the only documented way to say which browser. for the other two forms the readme never says how packages/cli/src/launch.ts finds a browser: is it a hardcoded list of the usual per-OS paths, CHROME_PATH, which google-chrome, something else? and what's the failure mode when nothing is found — a clear error or a stack trace?

this matters for the CI gate specifically. "Zero runtime dependencies ... No Puppeteer, no Playwright" means nothing downloads a browser for me, so on a bare runner i have to install one and then tell liarjs where it went — and there's no documented flag or env var for that. if there is one (--executable-path?), it should be in the quickstart next to --headless.

related, and the reason i can't just guess: when it does launch locally, does it use my real chrome profile or a throwaway one? my daily profile has extensions that change the fingerprint, so "your local Chrome" scoring differently from a clean launch is the difference between a useful number and noise.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions