← Back to the directory
Community listing This entry is based on publicly available sources and was not created by the owner. Is this your website?
Claim for free
· Standard Standard-Status
llmstxt.info directory · Standard

test-proxy-recorder

test-proxy-recorder.devDeveloper Tools
Community listing llms.txt reachable AI Impact Score 90/100 · A

The organization test-proxy-recorder uses the llms.txt standard for better discoverability by AI systems. Industry: Developer Tools. The website test-proxy-recorder.dev provides its llms.txt at https://test-proxy-recorder.dev/llms.txt. Listed since 4 August 2026.

Under GDPR Art. 17 you can request the deletion of your data. Report a legal violation (Art. 16 DSA) →
llms.txt — current content Open ↗
# test-proxy-recorder > VCR for Playwright — record real HTTP + WebSocket traffic once, replay it deterministically on CI with the backend turned off. No hand-written mocks. Covers Next.js & TanStack Start SSR, browser, and WebSocket traffic. Node >= 20, MIT. Last updated: 2026-08-18. Canonical: <https://test-proxy-recorder.dev/llms.txt>. ## For AI coding agents — preferred path This package ships task-focused `SKILL.md` files via [@tanstack/intent](https://www.npmjs.com/package/@tanstack/intent). If your agent supports Intent, load those instead of this file — they are the maintained, deeper source: ```bash # in the user's project, once npm install --save-dev test-proxy-recorder npx @tanstack/intent@latest install # list skills discoverable from installed packages npx @tanstack/intent@latest list # load a specific skill into the current context npx @tanstack/intent@latest load test-proxy-recorder#proxy-setup ``` Available skills (under `node_modules/test-proxy-recorder/skills/`): | Skill | Type | When to load | |---|---|---| | `proxy-setup` | core | Installing the library, the proxy CLI, `playwright.config.ts` `webServer`, per-test fixtures, record/replay/transparent modes, secret redaction, the config file, and the record-once → commit → CI-replay lifecycle | | `nextjs-ssr` | framework | Next.js App Router: tagging server-side fetches with `registerProxyFetch` / `registerProxyAxios` / `createHeadersWithRecordingId`, the build-and-start vs `next dev` caveat, why the m […truncated]