Files
James Ritchie fade22015f Docs – v4 GA updates (#2298)
* Adds new features table to top of v4 upgrade guide

* Adds wait idempotency to wait-until, wait-for, and wait-for-token pages

* Adds new priority docs page and updates the v4 upgrade guide

* Adds new task lifecycle hooks

* Removes the message about requiring tasks to be exported

* Adds new global lifecycle hooks section

* Moves sections from upgrade guide into the table

* Adds hidden task page

* Improves the global lifecycle hooks section

* Updates middleware and locals section

* Adds new useWaitToken page to the react hooks section

* Adds a new ai.tool section

* Moves Docker (legacy) page into self-hosting section

* Removes known issues from v4 upgrade guide

* Replace “toolTask” with “ai.tool” in the Streams page example

* Renames guide to “Migrating from v3” and adds redirect

* Remove references to v4

* Removes changelog from migration guide

* The installation guide now references `@latest update`

* Changes all references from `/sdk/v3` to `/sdk`

* Updates @v4-beta to @latest

* Fixed broken link

* Fixes broken link

* Adds an upgrade to v4 using AI section

* Fixes 2 broken links

* Adds an entry for targetting preview branches

* Updates the run statuses

* Adds boolean helpers section to the runs and realtime pages

* Updates the concurrency page

* Updates the test page to include the new options

* Adds SDK and curl options for the preview branch targeting

* Updates new bulk actions page

* Remove the releasing concurrency section

* Got rid of some more @v4-beta mentions

* Improved rate limit docs

* Improved migrating docs

* Removed commented sections of the docs

* useWaitToken hook

* Fixed the description

* Fix for missing test image

---------

Co-authored-by: Matt Aitken <matt@mattaitken.com>
Co-authored-by: Dan <8297864+D-K-P@users.noreply.github.com>
2025-08-18 12:34:55 +01:00

170 lines
5.5 KiB
Plaintext

---
title: "Playwright"
sidebarTitle: "playwright"
description: "Use the playwright build extension to use Playwright with Trigger.dev"
---
If you are using [Playwright](https://playwright.dev/), you should use the Playwright build extension.
- Automatically installs Playwright and required browser dependencies
- Allows you to specify which browsers to install (chromium, firefox, webkit)
- Supports headless or non-headless mode
- Lets you specify the Playwright version, or auto-detects it
- Installs only the dependencies needed for the selected browsers to optimize build time and image size
<Note>
This extension only affects the build and deploy process, not the `dev` command.
</Note>
You can use it for a simple Playwright setup like this:
```ts
import { defineConfig } from "@trigger.dev/sdk";
import { playwright } from "@trigger.dev/build/extensions/playwright";
export default defineConfig({
project: "<project ref>",
// Your other config settings...
build: {
extensions: [
playwright(),
],
},
});
```
### Options
- `browsers`: Array of browsers to install. Valid values: `"chromium"`, `"firefox"`, `"webkit"`. Default: `["chromium"]`.
- `headless`: Run browsers in headless mode. Default: `true`. If set to `false`, a virtual display (Xvfb) will be set up automatically.
- `version`: Playwright version to install. If not provided, the version will be auto-detected from your dependencies (recommended).
<Warning>
Using a different version in your app than specified here will break things. We recommend not setting this option to automatically detect the version.
</Warning>
### Custom browsers and version
```ts
import { defineConfig } from "@trigger.dev/sdk";
import { playwright } from "@trigger.dev/build/extensions/playwright";
export default defineConfig({
project: "<project ref>",
build: {
extensions: [
playwright({
browsers: ["chromium", "webkit"], // optional, will use ["chromium"] if not provided
version: "1.43.1", // optional, will automatically detect the version if not provided
}),
],
},
});
```
### Headless mode
By default, browsers are run in headless mode. If you need to run browsers with a UI (for example, for debugging), set `headless: false`. This will automatically set up a virtual display using Xvfb.
```ts
import { defineConfig } from "@trigger.dev/sdk";
import { playwright } from "@trigger.dev/build/extensions/playwright";
export default defineConfig({
project: "<project ref>",
build: {
extensions: [
playwright({
headless: false,
}),
],
},
});
```
### Environment variables
The extension sets the following environment variables during the build:
- `PLAYWRIGHT_BROWSERS_PATH`: Set to `/ms-playwright` so Playwright finds the installed browsers
- `PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD`: Set to `1` to skip browser download at runtime
- `PLAYWRIGHT_SKIP_BROWSER_VALIDATION`: Set to `1` to skip browser validation at runtime
- `DISPLAY`: Set to `:99` if `headless: false` (for Xvfb)
## Managing browser instances
To prevent issues with waits and resumes, you can use middleware and locals to manage the browser instance. This will ensure the browser is available for the whole run, and is properly cleaned up on waits, resumes, and after the run completes.
Here's an example using `chromium`, but you can adapt it for other browsers:
```ts
import { logger, tasks, locals } from "@trigger.dev/sdk";
import { chromium, type Browser } from "playwright";
// Create a locals key for the browser instance
const PlaywrightBrowserLocal = locals.create<{ browser: Browser }>("playwright-browser");
export function getBrowser() {
return locals.getOrThrow(PlaywrightBrowserLocal).browser;
}
export function setBrowser(browser: Browser) {
locals.set(PlaywrightBrowserLocal, { browser });
}
tasks.middleware("playwright-browser", async ({ next }) => {
// Launch the browser before the task runs
const browser = await chromium.launch();
setBrowser(browser);
logger.log("[chromium]: Browser launched (middleware)");
try {
await next();
} finally {
// Always close the browser after the task completes
await browser.close();
logger.log("[chromium]: Browser closed (middleware)");
}
});
tasks.onWait("playwright-browser", async () => {
// Close the browser when the run is waiting
const browser = getBrowser();
await browser.close();
logger.log("[chromium]: Browser closed (onWait)");
});
tasks.onResume("playwright-browser", async () => {
// Relaunch the browser when the run resumes
// Note: You will have to have to manually get a new browser instance in the run function
const browser = await chromium.launch();
setBrowser(browser);
logger.log("[chromium]: Browser launched (onResume)");
});
```
You can then use `getBrowser()` in your task's `run` function to access the browser instance:
```ts
export const playwrightTestTask = task({
id: "playwright-test",
run: async () => {
const browser = getBrowser();
const page = await browser.newPage();
await page.goto("https://google.com");
await page.screenshot({ path: "screenshot.png" });
await page.close();
// Waits will gracefully close the browser
await wait.for({ seconds: 10 });
// On resume, we will re-launch the browser but you will have to manually get the new instance
const newBrowser = getBrowser();
const newPage = await newBrowser.newPage();
await newPage.goto("https://playwright.dev");
await newPage.screenshot({ path: "screenshot2.png" });
await newPage.close();
},
});
```