From 0ac4d82c14cc6f90182c17230b314185003bf833 Mon Sep 17 00:00:00 2001 From: isshaddad Date: Fri, 8 May 2026 08:27:01 -0400 Subject: [PATCH] docs(bun): note WebSocket limitation with remote browser connections --- docs/guides/frameworks/bun.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/guides/frameworks/bun.mdx b/docs/guides/frameworks/bun.mdx index 3b9f7ccce23..2e25292e5ee 100644 --- a/docs/guides/frameworks/bun.mdx +++ b/docs/guides/frameworks/bun.mdx @@ -10,12 +10,13 @@ import CliRunTestStep from "/snippets/step-run-test.mdx"; import CliViewRunStep from "/snippets/step-view-run.mdx"; - The trigger.dev CLI does not yet support Bun. So you will need to run the CLI using Node.js. - Bun will still be used to execute your tasks, even in the `dev` environment. + The trigger.dev CLI does not yet support Bun. So you will need to run the CLI using Node.js. Bun + will still be used to execute your tasks, even in the `dev` environment. - **Supported Bun version:** Deployed tasks run on Bun 1.3.3. For local development, use Bun 1.3.x for compatibility. + **Supported Bun version:** Deployed tasks run on Bun 1.3.3. For local development, use Bun 1.3.x + for compatibility. @@ -27,6 +28,7 @@ import CliViewRunStep from "/snippets/step-view-run.mdx"; ```bash mkdir -p ~/.bun/bin && ln -s $(which bun) ~/.bun/bin/bun ``` +- Bun's WebSocket client does not handle the `101 Switching Protocols` upgrade response correctly, so connecting to a remote browser via `puppeteer.connect()` / `playwright.connectOverCDP()` (e.g. BrowserBase, Browserless) fails silently — typically with an empty `{}` `ErrorEvent`. The remote session opens and immediately drops. **Workaround:** set `runtime: "node"` in `trigger.config.ts` for tasks that connect to a remote browser. ## Initial setup