> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/reporters/currents-playwright/compatibility.md).

# Compatibility Guide

Discover the compatible versions of @currents/playwright

### Compatibility Table

Use the following table to discover what versions of `@currents/playwright` to use:

| @playwright/test | @currents/playwright |
| ---------------- | -------------------- |
| 1.59.1           | 1.24.0, 2.0.0+       |
| 1.60.0+          | 2.0.0+               |

[Balanced sharding](https://docs.currents.dev/guides/parallelization-guide/balanced-sharding.md) requires `@playwright/test` 1.62.0 or later and `@currents/playwright` 2.10.0 or later. On an older Playwright, an opted-in build prints a warning and splits the tests the way Playwright does.

#### Notes

* **May 19 2026** `@playwright/test@1.60.0` introduced changes that require updating Currents reporter to version `2.0.0+`.
  * Currents Orchestration users, follow the [Migration Guide](https://docs.currents.dev/guides/ci-optimization/playwright-orchestration/playwright-orchestration-migration-guide.md)
  * If you are **not** using Currents Orchestration no additional changed required beyond version bump.

### Run Playwright with Bun

`@currents/playwright` works with Bun as the package manager and as the runtime that runs the tests. The reporter, `pwc` and `pwc-p` work the same as with Node. Tested with Bun 1.3.14 and 1.4.4.

Running the tests under Bun requires Playwright 1.65.0 or later. Earlier Playwright versions cannot load a TypeScript config or spec file under Bun and stop with `error: Unexpected !`.

Start Playwright, `pwc` and `pwc-p` by their command names or from a `package.json` script:

| Command                                                                                      | Runtime that runs the tests |
| -------------------------------------------------------------------------------------------- | --------------------------- |
| `bunx playwright test`, `bun run test`, `bunx pwc`, `bunx pwc-p run`                         | Node                        |
| `bunx --bun playwright test`, `bun run --bun test`, `bunx --bun pwc`, `bunx --bun pwc-p run` | Bun                         |

On a machine without Node, for example the `oven/bun` Docker image, Bun runs the tests with either form.

#### `bun test` fails

```
error: Playwright Test did not expect test() to be called here.
```

`bun test` starts Bun's own test runner, not Playwright. Run Playwright with `bunx playwright test`, or add a `"test": "playwright test"` script to `package.json` and run `bun run test`.

#### Commands that start a file path

Start Playwright, `pwc` and `pwc-p` by their command names, not by a path such as `node_modules/@playwright/test/cli.js` or `node_modules/@currents/playwright/dist/bin/pwc-p.js`:

* `pwc` and `pwc-p` started by path cannot find Playwright in `@currents/playwright` 2.7.0, under Node as well as Bun. `pwc` stops with `Command failed with ENOENT: playwright test`, `pwc-p run` with `Failed discovery for orchestration session`, and `pwc-p discover` with ``Failed to run `playwright test --list`. Is @playwright/test installed and on PATH?``
* Playwright started by path with `bun --bun` runs the tests under Bun, but the Currents reporter starts its test list scan with Node. On a machine without Node, the reporter prints `pwc-scanner failed` and `/usr/bin/env: 'node': No such file or directory`, and the run is recorded without the list of all tests in the suite.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/resources/reporters/currents-playwright/compatibility.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
