Skip to content
Back to skills

Playwright Webserver

ASecurity

This skill should be used when orchestrating Anvil, Hardhat node, or frontend servers from Playwright webServer config for DeFi E2E tests.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 22, 2026
testingnodetestingfrontend

Works with

  • terminal

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add cyotee/indexedex --skill playwright-webserver --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Playwright Webserver?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Playwright Webserver
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyotee-playwright-webserver/badge)](https://www.skillsdirectory.com/skills/cyotee-playwright-webserver)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: playwright-webserver
description: This skill should be used when orchestrating Anvil, Hardhat node, or frontend servers from Playwright webServer config for DeFi E2E tests.
license: MIT
---

# Playwright webServer Orchestration

`webServer` starts dependencies before tests and can run **multiple services**.

## Multi-service pattern (Anvil + app)

```ts
// playwright.config.ts
webServer: [
  {
    command: 'anvil --block-time 1',
    url: 'http://127.0.0.1:8545',
    reuseExistingServer: !process.env.CI,
    timeout: 120_000,
  },
  {
    command: 'npm run dev',
    url: 'http://127.0.0.1:3000',
    reuseExistingServer: !process.env.CI,
    timeout: 120_000,
    env: {
      // Point frontend RPC at local Anvil
      VITE_RPC_URL: 'http://127.0.0.1:8545',
      NEXT_PUBLIC_RPC_URL: 'http://127.0.0.1:8545',
    },
  },
],
```

## Why this matters for DeFi

| Need | How webServer helps |
|------|---------------------|
| Idempotent chain | Fresh Anvil each CI run |
| No manual terminals | One `playwright test` boots stack |
| Local iteration | `reuseExistingServer: !CI` keeps your dev Anvil/app |
| Forked mainnet | `anvil --fork-url $RPC --fork-block-number N` |

## Fork mode example

```ts
{
  command: `anvil --fork-url ${process.env.MAINNET_RPC_URL} --fork-block-number 19000000`,
  url: 'http://127.0.0.1:8545',
  reuseExistingServer: !process.env.CI,
}
```

## Health checks

Playwright waits until `url` returns success. For Anvil, `http://127.0.0.1:8545` works with JSON-RPC. For apps, use the homepage or a `/health` route.

## Hardhat alternative

```ts
{
  command: 'npx hardhat node',
  url: 'http://127.0.0.1:8545',
  reuseExistingServer: !process.env.CI,
}
```

Same fixture patterns apply; prefer Anvil for speed and Foundry cheatcode parity with Solidity tests.

## CI tips

- Set `reuseExistingServer: false` in CI (default via `!process.env.CI`)
- Install Foundry in CI before Playwright
- Export deterministic env: chain id `31337`, fixed mnemonic accounts

## Troubleshooting

| Symptom | Fix |
|---------|-----|
| Port in use | Kill stale anvil/node or enable reuse locally |
| App connects to wrong RPC | Pass RPC via webServer `env` |
| Timeout starting server | Raise `timeout`, check command logs with `DEBUG=pw:webserver` |

## See also

- `anvil-node` (foundry plugin)
- `defi-ui-testing-overview` — full stack layout

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…