[Bug]: Cannot run Playwright UI after npm init playwright@latest on WSL2 #34187
Comments
|
@RERepos This is unexpected, not sure what's happening. The error message is "Cannot navigate to invalid URL" - I wonder what's the URL? If you could run with |
|
@dgozman Thank you for your reply! I ran it on both computers. The outputs look very similar, but maybe have slight differences. I'll post the first computer here, then add another post with the second computer. This is the output from the Desktop: ~:pls-playwright-fromScratch$ DEBUG=pw:protocol,pw:browser npx playwright test --ui |
|
This is the output from the laptop: ~:pls-playwright-fromScratch$ DEBUG=pw:protocol,pw:browser npx playwright test --ui |
|
Thanks! |
|
Looks like Node.js 18 returns a number instead of a string 
Working on a fix! |
|
I'm not sure if we'll land the fix, given that this can also be worked around by updating Node.js to the latest v18 release. So if you need a fix now, update Node.js! See #34203 (comment) |
|
I upgraded to node v20.18.1, and Thanks for your helpl!!! |
Version
1.49.1
Steps to reproduce
Follow steps on https://playwright.dev/docs/intro
npm init playwright@latestnpx playwright test- works finenpx playwright show-report- works finenpx playwright test --ui- does not workExpected behavior
Expected to see the Playwright UI screen.
Actual behavior
Errors:
ProtocolError: Protocol error (Page.navigate): Cannot navigate to invalid URL
at /home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/chromium/crConnection.js:135:16
at new Promise ()
at CRSession.send (/home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/chromium/crConnection.js:131:12)
at FrameSession._navigate (/home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/chromium/crPage.js:506:41)
at CRPage.navigateFrame (/home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/chromium/crPage.js:166:41)
at Frame._gotoAction (/home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/frames.js:540:55)
at /home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/frames.js:524:74
at Frame.raceNavigationAction (/home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/frames.js:496:95)
at Frame._goto (/home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/frames.js:524:17)
at /home/rerozak/rozak_app_foundry/pls-playwright-fromScratch/node_modules/playwright-core/lib/server/frames.js:521:44 {
type: 'error',
method: 'Page.navigate',
logs: undefined
}
Additional context
I left comments on another thread, but I see it was already closed and they were using Mac anyhow.
I'm just trying to get started with Playwright, so I'm simply starting from the installation/intro page.
I've tried clean installs of both the JS and TS versions.
I've tried restarting the computers.
I know WSL is kind of in it's own world, so are there any special steps needed for this environ?
Environment
Computer 1: Desktop running Windows 11 System: OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa) CPU: (16) x64 Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz Memory: 14.87 GB / 15.50 GB Container: Yes Binaries: Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm IDEs: VSCode: 1.96.2 - /mnt/c/Users/rober/AppData/Local/Programs/Microsoft VS Code/bin/code Languages: Bash: 5.0.17 - /usr/bin/bash npmPackages: @playwright/test: ^1.49.1 => 1.49.1 Computer 2: Laptop running Windows 11 System: OS: Linux 5.15 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish) CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1235U Memory: 14.66 GB / 15.47 GB Container: Yes Binaries: Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm IDEs: VSCode: 1.96.2 - /mnt/c/Users/rober/AppData/Local/Programs/Microsoft VS Code/bin/code Languages: Bash: 5.1.16 - /usr/bin/bash npmPackages: @playwright/test: ^1.49.1 => 1.49.1 Addl info: I don't know if this is relevant. But, in the Turn On/Off Windows Features box, Virtual Machine Platform is checked, and Windows Hypervisor Platform is not checked.The text was updated successfully, but these errors were encountered: