You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -234,7 +234,7 @@ These GitHub repositories provide supplementary resources for Rush Stack:
234
234
|[/rigs/local-web-rig](./rigs/local-web-rig/)| A rig package for Web projects that build using Heft inside the RushStack repository. |
235
235
|[/rush-plugins/rush-litewatch-plugin](./rush-plugins/rush-litewatch-plugin/)| An experimental alternative approach for multi-project watch mode |
236
236
|[/vscode-extensions/debug-certificate-manager-vscode-extension](./vscode-extensions/debug-certificate-manager-vscode-extension/)| VS Code extension to manage debug TLS certificates and sync them to the VS Code workspace. Works with VS Code remote development (Codespaces, SSH, Dev Containers, WSL, VS Code Tunnels). |
237
-
|[/vscode-extensions/playwright-on-codespaces-vscode-extension](./vscode-extensions/playwright-on-codespaces-vscode-extension/)| VS Code extension to enable Playwright testing in GitHub Codespaces. |
237
+
|[/vscode-extensions/playwright-local-browser-server-vscode-extension](./vscode-extensions/playwright-local-browser-server-vscode-extension/)| VS Code extension to enable Playwright testing in remote VS Code environments (such as Codespaces, Dev Containers, VS Code Tunnels) while launching and driving the actual browser process on your local machine. |
238
238
|[/vscode-extensions/rush-vscode-command-webview](./vscode-extensions/rush-vscode-command-webview/)| Part of the Rush Stack VSCode extension, provides a UI for invoking Rush commands |
239
239
|[/vscode-extensions/rush-vscode-extension](./vscode-extensions/rush-vscode-extension/)| Enhanced experience for monorepos that use the Rush Stack toolchain |
Copy file name to clipboardExpand all lines: apps/playwright-browser-tunnel/README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,33 +5,33 @@ Run a Playwright browser server in one environment and drive it from another env
5
5
6
6
This package is intended for remote development / CI scenarios (for example: Codespaces, devcontainers, or a separate “browser host” machine) where you want tests to run “here” but the actual browser process to run “there”.
7
7
8
-
## Relationship to the Playwright on Codespaces VS Code extension
8
+
## Relationship to the Playwright Local Browser Server VS Code extension
9
9
10
-
This package is the core tunneling/runtime layer used by the **Playwright on Codespaces** VS Code extension (located at [vscode-extensions/playwright-on-codespaces-vscode-extension](../../vscode-extensions/playwright-on-codespaces-vscode-extension)).
10
+
This package is the core tunneling/runtime layer used by the **Playwright Local Browser Server** VS Code extension (located at [vscode-extensions/playwright-local-browser-server-vscode-extension](../../vscode-extensions/playwright-local-browser-server-vscode-extension)).
11
11
12
12
In a typical Codespaces workflow:
13
13
14
14
- Your **tests** run inside the Codespace and call `tunneledBrowserConnection()`.
15
-
-`tunneledBrowserConnection()` starts a WebSocket server (by default on port `3000`) that a browser host can attach to.
16
-
- The VS Code extension runs on the **UI side** and starts a `PlaywrightTunnel` which connects to `ws://127.0.0.1:3000`.
17
-
- In Codespaces, this works when port `3000` is forwarded to your local machine (VS Code port forwarding makes the remote port reachable as `localhost:3000`).
15
+
-`tunneledBrowserConnection()` starts a WebSocket server (by default on port `56767`) that a browser host can attach to.
16
+
- The VS Code extension runs on the **UI side** and starts a `PlaywrightTunnel` which connects to `ws://127.0.0.1:56767`.
17
+
- In Codespaces, this works when port `56767` is forwarded to your local machine (VS Code port forwarding makes the remote port reachable as `localhost:56767`).
18
18
- Once connected, the extension hosts the actual Playwright browser process locally, while your tests continue to run remotely.
19
19
20
20
The extension provides a UI wrapper around this library (start/stop commands, status bar state, and logs), while `@rushstack/playwright-browser-tunnel` provides the underlying protocol forwarding and browser lifecycle management.
21
21
22
22
### Detecting whether the VS Code extension is present
23
23
24
-
Some remote test fixtures want to detect whether the **Playwright on Codespaces** extension is installed/active (for example, to skip local-browser-only scenarios when the extension isn’t available).
24
+
Some remote test fixtures want to detect whether the **Playwright Local Browser Server** extension is installed/active (for example, to skip local-browser-only scenarios when the extension isn’t available).
25
25
26
-
The extension writes a marker file named `.playwright-codespaces-extension-installed.txt` into the remote environment’s `os.tmpdir()` using VS Code’s remote filesystem APIs.
26
+
The extension writes a marker file named `.playwright-local-browser-server-extension-installed.txt` into the remote environment’s `os.tmpdir()` using VS Code’s remote filesystem APIs.
27
27
28
28
On the remote side, `isExtensionInstalledAsync()` checks for that marker file and returns `true` if it exists:
0 commit comments