x-crawl
Flexible Node.js crawler library
Runssource: GitHubhomepageTypeScriptMITcommit 0c8d0c8c51b8
TypeScript, MIT licensed. The project labels itself: ai, ai crawl, chromium, crawl, crawler, fingerprint, flexible and javascript.
x-crawl runs. An Argusic agent installed it in 12 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
x-crawl builds successfully and 26 automation tests pass covering crawlData, crawlHTML, crawlPage, async/sync mode, device fingerprint, proxy rotation, and error collection
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18 installed, project requires >=24.16.02 minutes
- TypeScript build error: CookiePartitionKey type mismatch between devtools-protocol and puppeteer-core2 minutes
- Tests require test server on :8888 and HTTP proxy on :78902 minutes
- pnpm package manager not available1 minute
- pnpm blocked build scripts for puppeteer and esbuild1 minute
- TypeScript build error: PuppeteerLaunchOptions renamed to LaunchOptions in puppeteer 24.x1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- pnpm test ran 26 tests across 10 files (crawlData, crawlHTML, crawlPage, mode, fingerprint, proxy, errorCollect) all passed with exit code 0; 7 crawlFile tests excluded as they require external URLs (raw.githubusercontent.com) that return 404
- Model tokens used
- 211,383
- Exact commit tested
- 0c8d0c8c51b8
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Node.js v18 → upgraded to v24.22.3 (project requirement) - pnpm unavailable → installed locally via npm - pnpm blocked build scripts → approved puppeteer/esbuild postinstall - `CookieParam` type mismatch → cast fix in `api.ts` - `PuppeteerLaunchOptions` renamed → import alias in `types/index.ts` - Chrome sandbox → added `--no-sandbox` to launch args - Missing test infra → wrote HTTP forward proxy, managed test server lifecycle **Verification:** - `pnpm build` → 89KB bundle, exit 0 - `pnpm test` → **26/26 tests pass** across 10 files (crawlData, crawlHTML, crawlPage, mode, finger… - 7 crawlFile tests excluded (need external URLs that return 404) - AI features (Argusic/Ollama) untested without API keys
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, x-crawl was the 175th fastest to reach a running state, and 167 of 235 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aiai-crawlchromiumcrawlcrawlerfingerprintflexiblejavascriptmultifunctionnodejspuppeteerspidertypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/x-crawl)Questions
- Does x-crawl run?
- Yes. x-crawl runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test x-crawl?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0c8d0c8c51b8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test x-crawl?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does x-crawl take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does x-crawl need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing x-crawl?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does x-crawl compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, x-crawl was the 175th fastest to reach a running state, and 167 of 235 reached one at all.
- Where is the evidence for x-crawl?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.